Bug 1026694

Summary: [abrt] gnome-settings-daemon-3.10.1-2.fc20: _g_log_abort: Process /usr/libexec/gnome-settings-daemon was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Maciek Borzecki <maciek.borzecki>
Component: gnome-settings-daemonAssignee: Bastien Nocera <bnocera>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: bnocera, chris_taxi1, csouth3, ekanter, fmuellner, hedelao, joe, kupo, mastaizawfm, mclasen, nalimilan, ofourdan, pablo.iranzo, redhat-bugzilla, rstrode, theo148, tiagomatos
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/f289609d5ad03584fed40a4f8105d87175decf2a
Whiteboard: abrt_hash:b6d781c93e8cc07ff56829cdfa2491dc57bff7af
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-03-19 18:02:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Maciek Borzecki 2013-11-05 09:14:01 UTC 
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
Comment 1 Maciek Borzecki 2013-11-05 09:14:11 UTC 
Created attachment 819587 [details]
File: backtrace
Comment 2 Maciek Borzecki 2013-11-05 09:14:16 UTC 
Created attachment 819588 [details]
File: cgroup
Comment 3 Maciek Borzecki 2013-11-05 09:14:20 UTC 
Created attachment 819589 [details]
File: core_backtrace
Comment 4 Maciek Borzecki 2013-11-05 09:14:25 UTC 
Created attachment 819590 [details]
File: dso_list
Comment 5 Maciek Borzecki 2013-11-05 09:14:29 UTC 
Created attachment 819591 [details]
File: environ
Comment 6 Maciek Borzecki 2013-11-05 09:14:34 UTC 
Created attachment 819592 [details]
File: limits
Comment 7 Maciek Borzecki 2013-11-05 09:14:40 UTC 
Created attachment 819593 [details]
File: maps
Comment 8 Maciek Borzecki 2013-11-05 09:14:44 UTC 
Created attachment 819594 [details]
File: open_fds
Comment 9 Maciek Borzecki 2013-11-05 09:14:50 UTC 
Created attachment 819595 [details]
File: proc_pid_status
Comment 10 Maciek Borzecki 2013-11-05 09:14:55 UTC 
Created attachment 819596 [details]
File: var_log_messages
Comment 11 Matthias Clasen 2014-01-03 03:22:49 UTC 
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
Comment 12 Milan Bouchet-Valat 2014-02-16 20:12:14 UTC 
Matthias: any news about this bug? I've seen it with 3.10.2-2.
Comment 13 Milan Bouchet-Valat 2014-03-19 18:02:18 UTC 
Filed upstream.