Bug 909629

Summary: [abrt] gnome-settings-daemon-3.6.4-2.fc18: Process /usr/libexec/gnome-settings-daemon was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: y-miles
Component: gnome-settings-daemonAssignee: Bastien Nocera <bnocera>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: bnocera, kem, mkasik, rstrode, tiagomatos
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:7c7ba509e8c47bc64db6dcc06aec23c1d85a077a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 19:04:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: build_ids
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: smolt_data none

Description y-miles 2013-02-09 23:47:20 UTC 
Version-Release number of selected component:
gnome-settings-daemon-3.6.4-2.fc18

Additional info:
backtrace_rating: 3
cmdline:        /usr/libexec/gnome-settings-daemon
executable:     /usr/libexec/gnome-settings-daemon
kernel:         3.7.5-201.fc18.x86_64
remote_result:  766859
uid:            1000
var_log_messages: Feb  8 14:07:28 babaganoush abrt[4215]: Saved core dump of pid 1928 (/usr/libexec/gnome-settings-daemon) to /var/spool/abrt/ccpp-2013-02-08-14:07:28-1928 (68493312 bytes)

Truncated backtrace:
Thread no. 1 (6 frames)
 #0 ??
 #1 g_simple_async_result_complete at gsimpleasyncresult.c:775
 #2 g_dbus_connection_call_done at gdbusconnection.c:5333
 #3 g_simple_async_result_complete at gsimpleasyncresult.c:775
 #4 complete_in_idle_cb at gsimpleasyncresult.c:787
 #9 gtk_main at gtkmain.c:1160
Comment 1 y-miles 2013-02-09 23:47:27 UTC 
Created attachment 695596 [details]
File: backtrace
Comment 2 y-miles 2013-02-09 23:47:30 UTC 
Created attachment 695597 [details]
File: build_ids
Comment 3 y-miles 2013-02-09 23:47:33 UTC 
Created attachment 695598 [details]
File: cgroup
Comment 4 y-miles 2013-02-09 23:47:36 UTC 
Created attachment 695599 [details]
File: core_backtrace
Comment 5 y-miles 2013-02-09 23:47:41 UTC 
Created attachment 695600 [details]
File: dso_list
Comment 6 y-miles 2013-02-09 23:47:44 UTC 
Created attachment 695601 [details]
File: environ
Comment 7 y-miles 2013-02-09 23:47:47 UTC 
Created attachment 695602 [details]
File: limits
Comment 8 y-miles 2013-02-09 23:47:52 UTC 
Created attachment 695603 [details]
File: maps
Comment 9 y-miles 2013-02-09 23:47:54 UTC 
Created attachment 695604 [details]
File: open_fds
Comment 10 y-miles 2013-02-09 23:47:57 UTC 
Created attachment 695605 [details]
File: proc_pid_status
Comment 11 y-miles 2013-02-09 23:48:00 UTC 
Created attachment 695606 [details]
File: smolt_data
Comment 12 Fedora End Of Life 2013-12-21 11:17:37 UTC 
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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.
Comment 13 Fedora End Of Life 2014-02-05 19:04:09 UTC 
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.