Hide Forgot
Description of problem: Crash icon showed directly after log in into cinnamon. Version-Release number of selected component: cinnamon-settings-daemon-1.0.0-0.14.gitcb4d724.fc19 Additional info: reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: /usr/libexec/cinnamon-settings-daemon crash_function: _gdk_x11_display_error_event executable: /usr/libexec/cinnamon-settings-daemon kernel: 3.11.1-200.fc19.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 _gdk_x11_display_error_event at gdkdisplay-x11.c:2556 #5 handle_error at xcb_io.c:213 #7 XRRSetCrtcConfig at XrrCrtc.c:147 #8 gnome_rr_crtc_set_config_with_time at gnome-rr.c:2188 #9 configure_crtc at gnome-rr-config.c:1600 #10 g_hash_table_foreach at ghash.c:1526 #11 crtc_assignment_apply at gnome-rr-config.c:1945 #12 gnome_rr_config_apply_with_time at gnome-rr-config.c:1308 #13 apply_configuration at csd-xrandr-manager.c:499 #14 turn_off_laptop_display at csd-xrandr-manager.c:1972
Created attachment 804310 [details] File: backtrace
Created attachment 804311 [details] File: cgroup
Created attachment 804312 [details] File: core_backtrace
Created attachment 804313 [details] File: dso_list
Created attachment 804314 [details] File: environ
Created attachment 804315 [details] File: limits
Created attachment 804316 [details] File: maps
Created attachment 804317 [details] File: open_fds
Created attachment 804318 [details] File: proc_pid_status
Created attachment 804319 [details] File: var_log_messages
Hi Oliver, Is the crash reproducible?
Not exactly, but here is what I think happened: After some update, the behavior of the power-off button changed from suspend to shutdown (is that a bug or a feature???), so for a while I would accidentally trigger a shutdown from a full session when I meant to suspend only. On reboot, this crash and others in cinnamon tend to come up (I only chose to file this one, after that I got tired of it). It's not strictly reproducible, in particular directly after a login, nothing happens. It seems to require a mature session.
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.