Description of problem: Changing default font in gtk-chtheme while running XFCE4 session. Version-Release number of selected component: xfwm4-4.10.1-2.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: xfwm4 --display :0.0 --sm-client-id 273701ee7-0c49-4ae5-b572-643b51a832ea crash_function: set_reload executable: /usr/bin/xfwm4 kernel: 3.12.5-302.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (7 frames) #0 set_reload at events.c:2681 #1 client_event_cb at events.c:2753 #2 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86 #7 gtk_widget_event_internal at gtkwidget.c:5017 #8 gtk_widget_event at gtkwidget.c:4814 #9 gtk_main_do_event at gtkmain.c:1639 #15 gtk_main at gtkmain.c:1257 Potential duplicate: bug 1029158
Created attachment 844204 [details] File: backtrace
Created attachment 844205 [details] File: cgroup
Created attachment 844206 [details] File: core_backtrace
Created attachment 844207 [details] File: dso_list
Created attachment 844208 [details] File: environ
Created attachment 844209 [details] File: exploitable
Created attachment 844210 [details] File: limits
Created attachment 844211 [details] File: maps
Created attachment 844212 [details] File: open_fds
Created attachment 844213 [details] File: proc_pid_status
Created attachment 844214 [details] File: var_log_messages
Any particular font? Or any font?
Seems to any font.
Perhaps this is a bug in gtk-chtheme, adding the maintainer there for comment. In the mean time perhaps you could use xfce-theme-manager ?
Well, the issue does not actually affect a user, as the window manager is immediately re-started. However, I am not sure if xfce-theme-manager sets theme got GTK+ application. There might be (also) a bug in gtk-chtheme, but no application should generate segmentation fault in any circumstances.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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 this bug is closed as described in the policy above. 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.