| Summary: | [abrt] gnome-settings-daemon-2.91.9-4.fc15: __libc_start_main: Process /usr/libexec/gnome-settings-daemon was killed by signal 11 (SIGSEGV) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Kjartan Maraas <kmaraas> | ||||||
| Component: | gnome-settings-daemon | Assignee: | Bastien Nocera <bnocera> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | rawhide | CC: | bnocera, jfrieben, jreiser, koggelmander, mclasen, me, raphoszap, redwolfe, rstrode, tla | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | i686 | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | abrt_hash:9bdf0d44ada1db2c84ae5ee10b55abfb860ce7d4 | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2011-12-14 16:26: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: | |||||||
| Attachments: |
|
||||||||
|
Description
Kjartan Maraas
2011-02-14 21:52:23 UTC
Created attachment 478719 [details]
File: backtrace
Looks like it is segfaulting in the atexit handlers. So there is 2 questions here: 1) Why would g-s-d exit at session start 2) Who installs an atexit handler from a loadable module that is already unloaded at that point to answer the second question: orbit does, when it gets pulled in via gconf use in the keybinding module - I guess we need to link g-s-d against gconf as long as any modules use it. Package: gnome-settings-daemon-2.91.9-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Rawhide) How to reproduce ----- 1.boot 2.login 3. Package: gnome-settings-daemon-2.91.9-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Rawhide) How to reproduce ----- 1. Start Fedora 15 Alpha TC2 2. Login 3. Comment ----- A new crach report is created very time I login Package: gnome-settings-daemon-2.91.9-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Rawhide) How to reproduce ----- 1. Logged in to GNOME. Package: gnome-settings-daemon-2.91.9-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Rawhide) How to reproduce ----- 1. Login GNOME. Package: gnome-settings-daemon-2.91.9-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) How to reproduce ----- 1.Happend at fedora start 2.I don't know... 3. Package: gnome-settings-daemon-2.91.9-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) How to reproduce ----- 1. normal login after latest updates 2. 3. Comment ----- gdm login screen crashes after first character typed on first attemt. Subsequent attempts accept full password but fail to start gnome. (In reply to comment #9) > Subsequent attempts accept full password but fail to start gnome. This is bug 678825. Use the mouse in order to confirm the password or downgrade to ibus-1.3.99.20110206-1.fc15. Package: gnome-settings-daemon-2.91.9-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) How to reproduce ----- 1.Automatic login into gnome 2. 3. Created attachment 480455 [details]
backtrace
gnome-settings-daemon-2.91.9-4.fc15 crashs on login
Package: gnome-settings-daemon-2.91.9-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) How to reproduce ----- 1. happens at boot 2. 3. Package: gnome-settings-daemon-2.91.9-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) How to reproduce ----- 1. this bug occurs at system startup. 2. every time 3. Probably fixed a long time ago by now? |