Bug 680639 - [abrt] gnome-settings-daemon-2.91.90-3.fc15: g_object_unref: Process /usr/libexec/gnome-settings-daemon was killed by signal 11 (SIGSEGV)
Summary: [abrt] gnome-settings-daemon-2.91.90-3.fc15: g_object_unref: Process /usr/lib...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-settings-daemon
Version: rawhide
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:283070a81575936c5f60d1358d1...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-26 16:00 UTC by Cédric OLIVIER
Modified: 2011-03-16 16:50 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-16 16:50:17 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (18.32 KB, text/plain)
2011-02-26 16:00 UTC, Cédric OLIVIER
no flags Details

Description Cédric OLIVIER 2011-02-26 16:00:36 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 18762 bytes
cmdline: /usr/libexec/gnome-settings-daemon
component: gnome-settings-daemon
Attached file: coredump, 46796800 bytes
crash_function: g_object_unref
executable: /usr/libexec/gnome-settings-daemon
kernel: 2.6.38-0.rc6.git4.1.fc15.x86_64
package: gnome-settings-daemon-2.91.90-3.fc15
rating: 4
reason: Process /usr/libexec/gnome-settings-daemon was killed by signal 11 (SIGSEGV)
release: Fedora release 16 (Rawhide)
time: 1298731403
uid: 500

How to reproduce
-----
1.Trying to launch gnome
2.
3.

Comment 1 Cédric OLIVIER 2011-02-26 16:00:40 UTC
Created attachment 481160 [details]
File: backtrace

Comment 2 Bastien Nocera 2011-03-16 16:50:17 UTC
I don't see how that could happen, but I added more checks, and safe-guards around this code in gnome-settings-daemon master.

commit e98c9079eec9cd9f6f27dd7813d96d6ba536e6c2
Author: Bastien Nocera <hadess>
Date:   Wed Mar 16 16:43:01 2011 +0000

    plugins: Make sure we mop up stray idle handlers


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