Bug 650587 - [abrt] gnome-color-manager-2.32.0-2.fc14: raise: Process /usr/bin/gcm-session was killed by signal 6 (SIGABRT)
Summary: [abrt] gnome-color-manager-2.32.0-2.fc14: raise: Process /usr/bin/gcm-session...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: sane-backends
Version: 14
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Nils Philippsen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:ab5883785a4ea578baa5bd6c988...
: 689580 694573 694575 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-07 08:31 UTC by Davide Prade
Modified: 2012-08-16 19:40 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-08-16 19:40:20 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (24.89 KB, text/plain)
2010-11-07 08:31 UTC, Davide Prade
no flags Details


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

Internal Links: 694575 694576

Description Davide Prade 2010-11-07 08:31:24 UTC
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: /usr/bin/gcm-session
component: gnome-color-manager
crash_function: raise
executable: /usr/bin/gcm-session
kernel: 2.6.35.6-48.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: 1289118173
uid: 500

Comment 1 Davide Prade 2010-11-07 08:31:27 UTC
Created attachment 458433 [details]
File: backtrace

Comment 2 Nils Philippsen 2011-04-04 11:41:07 UTC
A new upstream version with many bugfixes and enhancements has been released. Please check whether you issue persists with this updated package:

https://admin.fedoraproject.org/updates/sane-backends-1.0.22-1.fc14

Comment 3 Davide Prade 2011-04-07 17:02:10 UTC
The sane-backends version 1.0.22 doesn't work.

I opened the bugs 694575,694576 with the new backtraces.

Comment 4 abrt-bot 2012-03-21 15:30:25 UTC
*** Bug 689580 has been marked as a duplicate of this bug. ***

Comment 5 abrt-bot 2012-03-21 15:30:34 UTC
*** Bug 694573 has been marked as a duplicate of this bug. ***

Comment 6 abrt-bot 2012-03-21 15:30:43 UTC
*** Bug 694575 has been marked as a duplicate of this bug. ***

Comment 7 Fedora End Of Life 2012-08-16 19:40:22 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


Note You need to log in before you can comment on or make changes to this bug.