Version-Release number of selected component: emerald-0.8.8-5.fc18 Additional info: backtrace_rating: 4 cmdline: emerald-theme-manager crash_function: set_img_file executable: /usr/bin/emerald-theme-manager kernel: 3.8.8-202.fc18.x86_64 uid: 500 ureports_counter: 1 var_log_messages: Apr 24 22:40:16 abruce2 abrt[2231]: Saved core dump of pid 2196 (/usr/bin/emerald-theme-manager) to /var/tmp/abrt/ccpp-2013-04-24-22:40:16-2196 (63361024 bytes) xsession_errors: Truncated backtrace: Thread no. 1 (10 frames) #6 set_img_file at themer.c:639 #7 read_setting at themer.c:754 #8 g_slist_foreach at gslist.c:894 #9 cb_load at main.c:375 #10 _g_closure_invoke_va at gclosure.c:840 #13 _gtk_tree_selection_internal_select_node at gtktreeselection.c:1427 #15 gtk_tree_view_real_set_cursor at gtktreeview.c:12595 #16 gtk_tree_view_button_press at gtktreeview.c:2797 #17 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86 #22 gtk_widget_event_internal at gtkwidget.c:5017
Created attachment 740875 [details] File: backtrace
Created attachment 740876 [details] File: cgroup
Created attachment 740877 [details] File: core_backtrace
Created attachment 740878 [details] File: dso_list
Created attachment 740879 [details] File: environ
Created attachment 740880 [details] File: limits
Created attachment 740881 [details] File: maps
Created attachment 740882 [details] File: open_fds
Created attachment 740883 [details] File: proc_pid_status
Can you pls give more details info what you did if abrt was trigered? Did emerald crash? Did the emerald-theme-manager crash? Does this happens all the time or randomly? Which did you used if abrt was trigered?
(In reply to comment #10) > Can you pls give more details info what you did if abrt was trigered? > Did emerald crash? > Did the emerald-theme-manager crash? > Does this happens all the time or randomly? > Which did you used if abrt was trigered? I meant which emerald theme you used?
I was switching between themes at the time so, apologies but I do not know which caused the abrt. It seems to happen randomly.
Did emerald-theme-manager totally crashed or only triggered abrt?
(In reply to comment #13) > Did emerald-theme-manager totally crashed or only triggered abrt? It only triggered the abort.
Ok, i notice same was happend one time on my system after a fresh installation and the first use of emerald-theme-manger. Than never again. Pls, can you notice me if that happens again?
Was trying to close the Emerald theme manager. reporter: libreport-2.1.4 backtrace_rating: 4 cmdline: /usr/bin/emerald-theme-manager crash_function: set_img_file executable: /usr/bin/emerald-theme-manager kernel: 3.9.4-200.fc18.x86_64 package: emerald-0.8.8-6.fc18 reason: Process /usr/bin/emerald-theme-manager was killed by signal 6 (SIGABRT) runlevel: N 5 uid: 1000
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.