Version-Release number of selected component: xfce4-settings-4.10.1-3.fc20 Additional info: reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: xfce4-display-settings crash_function: g_type_check_instance_cast executable: /usr/bin/xfce4-display-settings kernel: 3.13.7-200.fc20.i686+PAE runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_type_check_instance_cast at gtype.c:4003 #1 xfconf_g_property_channel_notify at xfconf-binding.c:250 #2 _xfconf_marshal_VOID__STRING_BOXED at xfconf-marshal.c:123 #7 xfconf_channel_property_changed at xfconf-channel.c:392 #8 _xfconf_marshal_VOID__STRING_STRING_BOXED at xfconf-marshal.c:85 #13 xfconf_cache_set at xfconf-cache.c:819 #14 xfconf_channel_set_internal at xfconf-channel.c:408 #15 IA__xfconf_channel_set_bool at xfconf-channel.c:1219 #16 xfce_randr_save_output at xfce-randr.c:384 #17 xfce_randr_save_all at xfce-randr.c:460 Potential duplicate: bug 754201
Created attachment 880984 [details] File: backtrace
Created attachment 880985 [details] File: cgroup
Created attachment 880986 [details] File: core_backtrace
Created attachment 880987 [details] File: dso_list
Created attachment 880988 [details] File: environ
Created attachment 880989 [details] File: limits
Created attachment 880990 [details] File: maps
Created attachment 880991 [details] File: open_fds
Created attachment 880992 [details] File: proc_pid_status
Created attachment 880993 [details] File: var_log_messages
Created attachment 880994 [details] File: exploitable
Does this crash happen reproducibly or is this an isolated incident?
It happens first time. I'm not sure that I trace my manipulations correct but I tried to activate display before switch it on. Then I deactivated netbook's diaplay and swich external display on. Then I activated netbook's display, deactivated and activated external diaply again. And than xfce4-display-settings was crashed.
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.