Bug 592657 - [abrt] crash in gnome-settings-daemon-2.30.1-6.fc13: Process /usr/libexec/gnome-settings-daemon was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in gnome-settings-daemon-2.30.1-6.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:7aa1997e8e2ec2df77d0a76ca68...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-16 00:27 UTC by Oded Arbel
Modified: 2010-05-25 11:29 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-05-25 10:36:47 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (24.23 KB, text/plain)
2010-05-16 00:27 UTC, Oded Arbel
no flags Details

Description Oded Arbel 2010-05-16 00:27:36 UTC
abrt 1.1.0 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/gnome-settings-daemon
comment: Got a crash when session started
component: gnome-settings-daemon
crash_function: gkbd_indicator_config_load_font
executable: /usr/libexec/gnome-settings-daemon
global_uuid: 7aa1997e8e2ec2df77d0a76ca68f2add6e72e11a
kernel: 2.6.33.3-85.fc13.x86_64
package: gnome-settings-daemon-2.30.1-6.fc13
rating: 4
reason: Process /usr/libexec/gnome-settings-daemon was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

Comment 1 Oded Arbel 2010-05-16 00:27:39 UTC
Created attachment 414305 [details]
File: backtrace

Comment 2 Karel Klíč 2010-05-25 10:36:47 UTC

*** This bug has been marked as a duplicate of bug 592158 ***

Comment 3 Karel Klíč 2010-05-25 10:36:47 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.

Comment 4 Oded Arbel 2010-05-25 11:29:39 UTC
Will there be an updated version of ABRT to fix this, and should I avoid reporting additional crashes until a new ABRT version lands in Fedora 13?


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