Bug 593053

Summary: [abrt] crash in gnome-settings-daemon-2.30.1-5.fc13: Process /usr/libexec/gnome-settings-daemon was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: boucher.samuel.c
Component: gnome-settings-daemonAssignee: Bastien Nocera <bnocera>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: bnocera, mcepl, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:cb4e4c3d6e48567d0d13d90ae4472f886fe10a86
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-13 22:10:31 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

Description boucher.samuel.c 2010-05-17 17:59:41 UTC 
abrt 1.1.0 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/gnome-settings-daemon
component: gnome-settings-daemon
crash_function: gkbd_indicator_config_load_font
executable: /usr/libexec/gnome-settings-daemon
global_uuid: cb4e4c3d6e48567d0d13d90ae4472f886fe10a86
kernel: 2.6.33.3-85.fc13.x86_64
package: gnome-settings-daemon-2.30.1-5.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. start my comp
2.boot on fedora
3.log on my user
Comment 1 boucher.samuel.c 2010-05-17 17:59:43 UTC 
Created attachment 414628 [details]
File: backtrace
Comment 2 boucher.samuel.c 2010-05-18 12:17:47 UTC 
Package: gnome-settings-daemon-2.30.1-5.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. start my comp
2.boot on fedora
3.log on my user


Comment
-----
with gnome-shell active
Comment 3 Matěj Cepl 2010-07-13 22:10:31 UTC 

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