Version-Release number of selected component: gnome-settings-daemon-3.10.1-2.fc20 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/libexec/gnome-settings-daemon crash_function: _g_log_abort executable: /usr/libexec/gnome-settings-daemon kernel: 3.11.6-302.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 _g_log_abort at gmessages.c:255 #5 external_monitor_is_connected at gpm-common.c:1724 #6 suspend_on_lid_close at gsd-power-manager.c:2040 #7 on_randr_event at gsd-power-manager.c:3158 #8 on_rr_screen_acquired at gsd-power-manager.c:3237 #9 g_task_return_now at gtask.c:1108 #10 g_task_return at gtask.c:1161 #11 on_proxy_acquired at gnome-rr.c:625 #12 g_simple_async_result_complete at gsimpleasyncresult.c:777 #13 complete_in_idle_cb at gsimpleasyncresult.c:789
Created attachment 819587 [details] File: backtrace
Created attachment 819588 [details] File: cgroup
Created attachment 819589 [details] File: core_backtrace
Created attachment 819590 [details] File: dso_list
Created attachment 819591 [details] File: environ
Created attachment 819592 [details] File: limits
Created attachment 819593 [details] File: maps
Created attachment 819594 [details] File: open_fds
Created attachment 819595 [details] File: proc_pid_status
Created attachment 819596 [details] File: var_log_messages
From looking at the code, it seems that gsd-power-manager.c:on_rr_screen_acquired should check if gnome_rr_screen_new_finish returns an error
Matthias: any news about this bug? I've seen it with 3.10.2-2.
Filed upstream.