Bug 702543 - [abrt] gnome-color-manager-2.32.0-2.fc14: __libc_message: Process /usr/bin/gcm-prefs was killed by signal 6 (SIGABRT)
Summary: [abrt] gnome-color-manager-2.32.0-2.fc14: __libc_message: Process /usr/bin/gc...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-color-manager
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:1be28a8d0b2677b99ecab31623d...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-06 04:57 UTC by flibitijibibo
Modified: 2011-11-15 12:34 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-15 12:34:17 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (18.39 KB, text/plain)
2011-05-06 04:57 UTC, flibitijibibo 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description flibitijibibo 2011-05-06 04:57:02 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 18834 bytes
cmdline: gcm-prefs
component: gnome-color-manager
Attached file: coredump, 39976960 bytes
crash_function: __libc_message
executable: /usr/bin/gcm-prefs
kernel: 2.6.35.12-90.fc14.x86_64
package: gnome-color-manager-2.32.0-2.fc14
rating: 4
reason: Process /usr/bin/gcm-prefs was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1304657681
uid: 500

How to reproduce
-----
1. Opened Color Profiles
2. Closed Color Profiles
3. Kersplode!
Comment 1 flibitijibibo 2011-05-06 04:57:04 UTC 
Created attachment 497284 [details]
File: backtrace
Comment 2 zuperkoleoptera 2011-05-22 19:53:09 UTC 
Package: gnome-color-manager-2.32.0-2.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.After installing XFCE in a Fedora 14 32bit installation. First login without a reboot.
Comment 3 Richard Hughes 2011-11-15 12:34:17 UTC 
You need to either use F15 or F16 at this stage, sorry.
Note You need to log in before you can comment on or make changes to this bug.