Version-Release number of selected component: xfce4-settings-4.10.0-4.fc18 Additional info: backtrace_rating: 3 cmdline: xfce4-appearance-settings --socket-id=58721376 executable: /usr/bin/xfce4-appearance-settings kernel: 3.8.4-202.fc18.x86_64 uid: 1000 ureports_counter: 1 var_log_messages: Mar 26 11:34:49 croozah abrt[6397]: Saved core dump of pid 6317 (/usr/bin/xfce4-appearance-settings) to /var/tmp/abrt/ccpp-2013-03-26-11:34:49-6317 (22437888 bytes) xsession_errors: Truncated backtrace: Thread no. 1 (8 frames) #0 ?? #5 gtk_object_dispose at gtkobject.c:421 #7 _gtk_plug_send_delete_event at gtkplug.c:383 #8 _gtk_plug_windowing_filter_func at gtkplug-x11.c:280 #9 gdk_event_apply_filters at gdkevents-x11.c:356 #10 gdk_event_translate at gdkevents-x11.c:1052 #11 _gdk_events_queue at gdkevents-x11.c:2336 #17 gtk_main at gtkmain.c:1257
Created attachment 716591 [details] File: backtrace
Created attachment 716592 [details] File: cgroup
Created attachment 716593 [details] File: core_backtrace
Created attachment 716594 [details] File: dso_list
Created attachment 716595 [details] File: environ
Created attachment 716596 [details] File: limits
Created attachment 716597 [details] File: maps
Created attachment 716598 [details] File: open_fds
Created attachment 716599 [details] File: proc_pid_status
Created attachment 716600 [details] File: smolt_data
What were you doing when this happened? Can you duplicate it?
This occurred upon start of XFCE session / at login. Yes it can be reproduced each login. joe
Do you have a non default theme or setting in appearence settings? Can you think of what might have changed when this started happening?
This initial bug report occurred upon installing XFCE and starting it for the first time, thus no modifications had been made. XFCE was installed from Fedora repos -> Package Groups, selected xfce-desktop and xfce-apps. Please let me know of any additional information you need. joe
Thanks. Will see what I can make of the traceback...
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.