Bug 593053 - [abrt] crash in gnome-settings-daemon-2.30.1-5.fc13: Process /usr/libexec/gnome-settings-daemon was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in gnome-settings-daemon-2.30.1-5.fc13: Process /usr/libexec/gno...
Status: CLOSED DUPLICATE of bug 611580
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:cb4e4c3d6e48567d0d13d90ae44...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-17 17:59 UTC by boucher.samuel.c
Modified: 2018-04-11 07:13 UTC (History)
3 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2010-07-13 22:10:31 UTC


Attachments (Terms of Use)
File: backtrace (24.38 KB, text/plain)
2010-05-17 17:59 UTC, boucher.samuel.c
no flags Details

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 ***


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