Bug 678114 - [abrt] gnome-color-manager-2.32.0-2.fc14: Process /usr/bin/gcm-prefs was killed by signal 6 (SIGABRT)
Summary: [abrt] gnome-color-manager-2.32.0-2.fc14: Process /usr/bin/gcm-prefs was kill...
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:bb4c5d77e2ef95790dcfe9c9ed6...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-16 19:04 UTC by constantine.hatzis
Modified: 2011-11-15 12:38 UTC (History)
2 users (show)

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

Attachments (Terms of Use)
File: backtrace (18.27 KB, text/plain)
2011-02-16 19:04 UTC, constantine.hatzis 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description constantine.hatzis 2011-02-16 19:04:19 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: gcm-prefs
component: gnome-color-manager
executable: /usr/bin/gcm-prefs
kernel: 2.6.35.11-83.fc14.x86_64
package: gnome-color-manager-2.32.0-2.fc14
reason: Process /usr/bin/gcm-prefs was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1297882888
uid: 500

How to reproduce
-----
1. Start gnome-color-manager from menu
2. Close gnome-color-manager using window close button
3.
Comment 1 constantine.hatzis 2011-02-16 19:04:21 UTC 
Created attachment 479194 [details]
File: backtrace
Comment 2 orion520a 2011-03-25 23:32:05 UTC 
Package: gnome-color-manager-2.32.0-2.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.Csak úgy
2.
3.
Comment 3 orion520a 2011-03-26 11:05:44 UTC 
Package: gnome-color-manager-2.32.0-2.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. I do not remember.
Comment 4 Richard Hughes 2011-11-15 12:38:16 UTC 
You need to either use F15 or F16 at this stage, sorry. Please re-open if it still happens in newer releases. Thanks.
Note You need to log in before you can comment on or make changes to this bug.