Bug 690306 - [abrt] control-center-1:2.91.92-1.fc15: __libc_message: Process /usr/bin/gnome-control-center was killed by signal 6 (SIGABRT)
Summary: [abrt] control-center-1:2.91.92-1.fc15: __libc_message: Process /usr/bin/gnom...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-color-manager
Version: 15
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:ad9799c3f348a4382fed49ed3eb...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-23 20:38 UTC by jimmy
Modified: 2011-04-27 13:10 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-27 13:10:30 UTC
Type: ---

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

Description jimmy 2011-03-23 20:38:08 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 41443 bytes
cmdline: gnome-control-center color
component: control-center
Attached file: coredump, 49647616 bytes
crash_function: __libc_message
executable: /usr/bin/gnome-control-center
kernel: 2.6.38-1.fc15.i686
package: control-center-1:2.91.92-1.fc15
rating: 3
reason: Process /usr/bin/gnome-control-center was killed by signal 6 (SIGABRT)
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: 1300911185
uid: 500
Comment 1 jimmy 2011-03-23 20:38:11 UTC 
Created attachment 487144 [details]
File: backtrace
Comment 2 Saurabh Rawat 2011-03-25 02:08:20 UTC 
Package: control-center-1:2.91.92-1.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)


How to reproduce
-----
1.changed wallpaper
2.
3.
Comment 3 Richard Hughes 2011-04-26 10:16:06 UTC 
This doesn't have all the debug symbols that I need -- does this still happen with 3.0.0?
Comment 4 jimmy 2011-04-26 14:59:48 UTC 
I havent seen it since the 3.0.0. release.

(In reply to comment #3)
> This doesn't have all the debug symbols that I need -- does this still happen
> with 3.0.0?
Note You need to log in before you can comment on or make changes to this bug.