Bug 668451 - [abrt] xsane-0.998-1.fc13: _XEventsQueued: Process /usr/bin/xsane was killed by signal 6 (SIGABRT)
Summary: [abrt] xsane-0.998-1.fc13: _XEventsQueued: Process /usr/bin/xsane was killed ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gtk2
Version: 14
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:7d9f1c32a555cbb6ea3c47629cf...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-10 14:57 UTC by mcl8
Modified: 2012-08-16 19:23 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 19:23:28 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (30.15 KB, text/plain)
2011-01-10 14:57 UTC, mcl8
no flags Details

Description mcl8 2011-01-10 14:57:12 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: xsane
comment: Happens every time I start xsane or xsane-gimp.  The xsane windows appear briefly, then it dumps.
component: xsane
crash_function: _XEventsQueued
executable: /usr/bin/xsane
kernel: 2.6.34.7-66.fc13.x86_64
package: xsane-0.998-1.fc13
rating: 4
reason: Process /usr/bin/xsane was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1294670457
uid: 1994

How to reproduce
-----
1. Start xsane from command line, or
2. From gimp, Create->Xsane: Device dialog
3.

Comment 1 mcl8 2011-01-10 14:57:14 UTC
Created attachment 472615 [details]
File: backtrace

Comment 2 Bug Zapper 2011-05-30 12:01:56 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 3 mcl8 2011-05-31 14:19:58 UTC
I no longer use Fedora 13, but xsane does not work on Fedora 14 (64-bit) either:

Gdk-ERROR **: The program 'xsane' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 18684 error_code 8 request_code 151 minor_code 5)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
aborting...
Abort (core dumped)

Comment 4 Nils Philippsen 2011-05-31 15:18:13 UTC
Sorry for dropping this, I should have noticed the BadMatch error right away. Changing component to the toolkit (gtk2) since xsane doesn't operate on X11, and therefore isn't likely to be the direct cause of this.

Comment 5 Fedora End Of Life 2012-08-16 19:23:31 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.