Bug 600234 - [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 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:88dcbb9921212054c2ef266aadd...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-04 08:30 UTC by Stefano Canepa
Modified: 2018-04-11 19:05 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-07-13 22:10:42 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (27.47 KB, text/plain)
2010-06-04 08:30 UTC, Stefano Canepa 		no flags Details
View All

Description Stefano Canepa 2010-06-04 08:30:41 UTC 
abrt 1.1.0 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/gnome-settings-daemon
comment: I was just trying to change my GTK theme to a darker one and then the gnome-setting-daemon crashed and all fonts suddenly appeared bigger the usual.
component: gnome-settings-daemon
crash_function: gkbd_indicator_config_load_font
executable: /usr/libexec/gnome-settings-daemon
global_uuid: 88dcbb9921212054c2ef266aadd064d0196a6c7e
kernel: 2.6.33.4-95.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)

How to reproduce
-----
1. Open gnome-appearance-properties to change the GTK theme
2. Select "Customize" (I'm guessing the English version of the button as I'm using Italian localization)
Comment 1 Stefano Canepa 2010-06-04 08:30:43 UTC 
Created attachment 421160 [details]
File: backtrace
Comment 2 Matěj Cepl 2010-07-13 22:10:42 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.