Version-Release number of selected component: mate-window-manager-1.6.2-7.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: marco crash_function: meta_screen_for_x_screen executable: /usr/bin/marco kernel: 3.15.6-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (6 frames) #0 meta_screen_for_x_screen at core/screen.c:844 #1 xrender_add_window at compositor/compositor-xrender.c:2473 #2 meta_screen_composite_all_windows at core/screen.c:826 #3 enable_compositor at core/display.c:289 #4 emit_changed at core/prefs.c:805 #5 changed_idle_handler at core/prefs.c:831 Potential duplicate: bug 978562
Created attachment 921536 [details] File: backtrace
Created attachment 921537 [details] File: cgroup
Created attachment 921538 [details] File: core_backtrace
Created attachment 921539 [details] File: dso_list
Created attachment 921540 [details] File: environ
Created attachment 921541 [details] File: limits
Created attachment 921542 [details] File: maps
Created attachment 921543 [details] File: open_fds
Created attachment 921544 [details] File: proc_pid_status
Created attachment 921545 [details] File: var_log_messages
Created attachment 921546 [details] File: exploitable
My cristal ball says you tried to enable compositor effect with dconf-editor. Right? ;) Why you guys alwaws create a report without a descripton and a way to reproduce? Do you think maintainers are gods or do you want to make our live harder as needed? Ok , stop joking ;) Whats happens?
I create some of the reports because ABRT pops up and advices me to make a report to help developers. "Consider to send a report", it asks me, and I send. In many times ABRT pops up unexpectedly in the middle of something, and it talks about components that are not known to me righ now. But because it asks — I press the button "send" to send. When it asks me what caused the bug, it offers option "i don't know", and may I activate the option as I really don't know. I think that automated context data like coredump and backtrace may help. I don't know the exact context of this bug, but it most likely relates to my recent installation of compiz. I was installing and configuring 2 or 3 components of compiz via yumex, played with several themes ("decorators"/GTK/Emerald), and met several errors and misconfigurations before finally getting the good configuration. I wasn't using dconf-editor.
Maybe ABRT should offer some options like making written notes to help myself to memorize the context while ABRT collects its data. It usually takes a long time and I may get far into doing something else before ABRT finishes collecting and offers the prompt "what I was dong?" — may be I should be able to write quick notes in separate field next to ABRT log output field. Maybe some user interface professionals should think on more friendly ABRT behavior for newbies.
Did the issue occours with marco-1.8.x ?
closed, package are renamed to marco