Version-Release number of selected component: gnome-settings-daemon-3.7.91-1.fc19 Additional info: backtrace_rating: 4 cmdline: /usr/libexec/gnome-settings-daemon crash_function: _gdk_x11_display_error_event executable: /usr/libexec/gnome-settings-daemon kernel: 3.9.0-0.rc1.git0.4.fc19.i686.PAE uid: 42 Truncated backtrace: Thread no. 1 (10 frames) #2 _gdk_x11_display_error_event at gdkdisplay-x11.c:2546 #5 handle_error at xcb_io.c:212 #6 handle_response at xcb_io.c:324 #8 XSyncListSystemCounters at XSync.c:347 #9 find_idletime_counter at gnome-idle-monitor.c:221 #10 init_xsync at gnome-idle-monitor.c:281 #11 gnome_idle_monitor_constructed at gnome-idle-monitor.c:352 #13 g_object_new_valist at gobject.c:1836 #15 gnome_idle_monitor_new_for_device at gnome-idle-monitor.c:416 #16 device_added_cb at gsd-cursor-manager.c:169 Potential duplicate: bug 799920
Created attachment 708751 [details] File: backtrace
Created attachment 708752 [details] File: cgroup
Created attachment 708753 [details] File: core_backtrace
Created attachment 708754 [details] File: dso_list
Created attachment 708755 [details] File: environ
Created attachment 708756 [details] File: limits
Created attachment 708757 [details] File: maps
Created attachment 708758 [details] File: open_fds
Created attachment 708759 [details] File: proc_pid_status
Created attachment 708760 [details] File: var_log_messages
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
After password prompt, Fedora displays a blank screen. If I boot with an external display connected, I can see Gnome3 in it, go to settings->displays, and see a third "Unknow monitor" there. I suspect this ghost monitor is linked to the problem. In order to be able to boot without an external display and/or fix the problem I have booted after adding to GRUB configuration the parameter "nomodeset". I have seen this error then. reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: /usr/libexec/gnome-settings-daemon crash_function: _gdk_x11_display_error_event executable: /usr/libexec/gnome-settings-daemon kernel: 3.9.9-301.fc19.x86_64 package: gnome-settings-daemon-3.8.3-3.fc19 reason: Process /usr/libexec/gnome-settings-daemon was killed by signal 5 (SIGTRAP) runlevel: N 5 uid: 1000
This is an X error triggered by the gnome-idletime code in gnome-desktop
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.