Bug 584275 - [abrt] crash in gnome-settings-daemon-2.30.0-1.fc13: Process /usr/libexec/gnome-settings-daemon was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in gnome-settings-daemon-2.30.0-1.fc13: Process /usr/libexec/gno...
Keywords:
Status: CLOSED DUPLICATE of bug 592158
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-settings-daemon
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:cf4c6bdec7e954df21ee40cd7d0...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-21 08:32 UTC by Fabien Archambault
Modified: 2010-05-25 10:36 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-25 10:36:14 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (24.93 KB, text/plain)
2010-04-21 08:32 UTC, Fabien Archambault 		no flags Details
View All

Description Fabien Archambault 2010-04-21 08:32:34 UTC 
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/gnome-settings-daemon
comment: It seems like the trayicons where not loaded from an old configuration
component: gnome-settings-daemon
executable: /usr/libexec/gnome-settings-daemon
global_uuid: cf4c6bdec7e954df21ee40cd7d070500152cb3fc
kernel: 2.6.33.2-57.fc13.x86_64
package: gnome-settings-daemon-2.30.0-1.fc13
rating: 4
reason: Process /usr/libexec/gnome-settings-daemon was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Update in the 21st april
2. Reboot
3. No trayicon available
4. Logout
5. Logon again
Comment 1 Fabien Archambault 2010-04-21 08:32:37 UTC 
Created attachment 408016 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 10:36:14 UTC 

*** This bug has been marked as a duplicate of bug 592158 ***
Comment 3 Karel Klíč 2010-05-25 10:36:14 UTC 
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #592158.

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