Bug 639420 - [abrt] xsane-0.997-10.fc13: raise: Process /usr/bin/xsane was killed by signal 6 (SIGABRT)
Summary: [abrt] xsane-0.997-10.fc13: raise: Process /usr/bin/xsane was killed by signa...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gtk2
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:c7d034656a88ad7a27c7cf36596...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-01 17:44 UTC by roger griffiths
Modified: 2011-06-28 12:06 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-28 12:06:13 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (34.13 KB, text/plain)
2010-10-01 17:44 UTC, roger griffiths
no flags Details

Description roger griffiths 2010-10-01 17:44:35 UTC
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: xsane
component: xsane
crash_function: raise
executable: /usr/bin/xsane
kernel: 2.6.34.7-56.fc13.x86_64
package: xsane-0.997-10.fc13
rating: 4
reason: Process /usr/bin/xsane was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1285954655
uid: 25561

comment
-----
Happens everytime.
running kernel-2.6.34.7-56.fc13.x86_64, with  kmod-nvidia-2.6.34.7-56.
Dual monitors.

How to reproduce
-----
1. Everytime I fire up xsane, either from the menu or at the command prompt it appears momentarily the disapears.
2.
3.

Comment 1 roger griffiths 2010-10-01 17:44:37 UTC
Created attachment 451068 [details]
File: backtrace

Comment 2 Nils Philippsen 2010-10-04 09:18:52 UTC
"BadMatch (invalid parameter attributes)" hints to a problem in the gtk or X stack, changing component to gtk2.

Comment 3 Bug Zapper 2011-05-31 12:10:34 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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

Comment 4 Bug Zapper 2011-06-28 12:06:13 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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