Bug 690304 - [abrt] gnome-settings-daemon-2.91.92-1.fc15: g_atomic_int_exchange_and_add: Process /usr/libexec/gnome-settings-daemon was killed by signal 11 (SIGSEGV)
Summary: [abrt] gnome-settings-daemon-2.91.92-1.fc15: g_atomic_int_exchange_and_add: P...
Keywords:
Status: CLOSED DUPLICATE of bug 692557
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-settings-daemon
Version: 15
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:e38b2be7a30c7345de65157ef6f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-23 20:33 UTC by jimmy
Modified: 2011-04-07 23:58 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-07 23:58:52 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (20.12 KB, text/plain)
2011-03-23 20:33 UTC, jimmy 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description jimmy 2011-03-23 20:33:49 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 20603 bytes
cmdline: /usr/libexec/gnome-settings-daemon
component: gnome-settings-daemon
Attached file: coredump, 36597760 bytes
crash_function: g_atomic_int_exchange_and_add
executable: /usr/libexec/gnome-settings-daemon
kernel: 2.6.38-1.fc15.i686
package: gnome-settings-daemon-2.91.92-1.fc15
rating: 3
reason: Process /usr/libexec/gnome-settings-daemon was killed by signal 11 (SIGSEGV)
release: Fedora release 15 (Lovelock)
How to reproduce: I have a fresh install of the Alpha running for testing/peek-lloking on my ASUS EEEPC 1000H with stock equipment. Sorry for not being able to give more details. I run look around in the release and check things out.
time: 1300911510
uid: 500
Comment 1 jimmy 2011-03-23 20:33:52 UTC 
Created attachment 487143 [details]
File: backtrace
Comment 2 Matthias Clasen 2011-04-07 23:58:52 UTC 

*** This bug has been marked as a duplicate of bug 692557 ***
Note You need to log in before you can comment on or make changes to this bug.