Bug 658925 - [abrt] gnome-settings-daemon-2.91.5-2.fc15: Process /usr/libexec/gnome-settings-daemon was killed by signal 11 (SIGSEGV)
Summary: [abrt] gnome-settings-daemon-2.91.5-2.fc15: Process /usr/libexec/gnome-settin...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-settings-daemon
Version: rawhide
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:fcdb2867fa011fe75884aa09a40...
: 659449 675801 681162 683500 684479 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-01 16:21 UTC by Raphos
Modified: 2018-04-11 15:59 UTC (History)
11 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-03-16 16:03:26 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (7.79 KB, text/plain)
2010-12-01 16:21 UTC, Raphos
no flags Details

Description Raphos 2010-12-01 16:21:10 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/gnome-settings-daemon
component: gnome-settings-daemon
executable: /usr/libexec/gnome-settings-daemon
kernel: 2.6.36.1-10.fc15.x86_64
package: gnome-settings-daemon-2.91.5-2.fc15
reason: Process /usr/libexec/gnome-settings-daemon was killed by signal 11 (SIGSEGV)
release: Fedora release 15 (Rawhide)
time: 1291220072
uid: 500

How to reproduce
-----
1.Use gnome-shell
2.
3.

Comment 1 Raphos 2010-12-01 16:21:12 UTC
Created attachment 464042 [details]
File: backtrace

Comment 2 Horst H. von Brand 2010-12-03 14:10:12 UTC
Package: gnome-settings-daemon-2.91.5-2.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Rawhide)


How to reproduce
-----
1. I asked to shut the machine down
2. It complained g-s-d was still running, I asked to kill it and log out anyway
3.


Comment
-----
Loged out, gnome-settings-daemon didn't shut down normally (killed by the "Log out anyway" window)

Comment 3 Jerry James 2010-12-14 19:13:30 UTC
Bug 659449 appears to be a duplicate of this one.

I booted up Rawhide, and got a black background on the GDM screen.  I logged in and everything seemed okay, so I ran abrt-gui as root to see if something had crashed.  I found that g-s-d had indeed crashed, with a backtrace that looks like the one in this report.

The crash is happening because g-s-d is exiting, and glibc is doing the atexit/on_exit function pointer handling, but some function on the list doesn't exist.  That is, the address on the list is not currently mapped.

The memory map in /var/spool/abrt for my crash looks like the one in this report.  But it is slightly different from the one that is running as I am logged in as a normal user.  It is missing /usr/lib64/libORBit-2.so.0.1.0, which does register a function with atexit, namely shutdown_orb.  Is there some way that libORBit could have been dlclose()d, but left shutdown_orb sitting on the atexit list?

Comment 4 Bastien Nocera 2011-03-16 16:01:54 UTC
*** Bug 659449 has been marked as a duplicate of this bug. ***

Comment 5 Bastien Nocera 2011-03-16 16:03:26 UTC
ORBit installs an atexit() handler to clean up GConf connections, but we don't use GConf in the main binary, only in the plugins that have been unloaded by then. Worked around in gnome-settings-daemon master.

commit 50720bce5a48b2a69eec57a74bb02f0774f5f127
Author: Bastien Nocera <hadess>
Date:   Mon Mar 14 17:39:14 2011 +0000

    main: Fix possible crasher on exit
    
    Because ORBit sucks, and installs an atexit() handler, even though
    it doesn't need one.
    
    https://bugzilla.gnome.org/show_bug.cgi?id=639347

Comment 6 Bastien Nocera 2011-03-16 16:08:00 UTC
*** Bug 683500 has been marked as a duplicate of this bug. ***

Comment 7 Bastien Nocera 2011-03-16 16:55:30 UTC
*** Bug 684479 has been marked as a duplicate of this bug. ***

Comment 8 Bastien Nocera 2011-03-16 16:55:53 UTC
*** Bug 681162 has been marked as a duplicate of this bug. ***

Comment 9 Bastien Nocera 2011-03-16 17:00:30 UTC
*** Bug 675801 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.