Bug 694576 - [abrt] gnome-color-manager-2.32.0-2.fc14: Process /usr/bin/gcm-session was killed by signal 6 (SIGABRT)
Summary: [abrt] gnome-color-manager-2.32.0-2.fc14: Process /usr/bin/gcm-session was ki...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-color-manager
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:ca1ad084d5710f6cd7b16672345...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-07 17:01 UTC by Davide Prade
Modified: 2011-11-15 12:36 UTC (History)
2 users (show)

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

Attachments (Terms of Use)
File: backtrace (26.23 KB, text/plain)
2011-04-07 17:01 UTC, Davide Prade 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 650587 0 low CLOSED [abrt] gnome-color-manager-2.32.0-2.fc14: raise: Process /usr/bin/gcm-session was killed by signal 6 (SIGABRT) 2021-02-22 00:41:40 UTC

Internal Links: 650587

Description Davide Prade 2011-04-07 17:01:21 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 26857 bytes
cmdline: /usr/bin/gcm-session
component: gnome-color-manager
Attached file: coredump, 39686144 bytes
crash_function: hp_optset_fix_geometry_options
executable: /usr/bin/gcm-session
kernel: 2.6.35.11-83.fc14.i686
package: gnome-color-manager-2.32.0-2.fc14
rating: 4
reason: Process /usr/bin/gcm-session was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1302195560
uid: 500

How to reproduce
-----
1. Open "Simple Scan"
2. Acquire single page
Comment 1 Davide Prade 2011-04-07 17:01:25 UTC 
Created attachment 490596 [details]
File: backtrace
Comment 2 Richard Hughes 2011-11-15 12:36: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.