Red Hat Bugzilla – Bug 869175
[abrt] xsane-0.998-12.fc17: read: Process /usr/bin/xsane was killed by signal 6 (SIGABRT)
Last modified: 2013-08-01 01:51:46 EDT
Description of problem:
I asked xsane to display one page from a multi-page project. That page was modified behind xsane's back using gimp.
The page never show, and xsane get stuck.
I killed it with SIGABRT to get a trace.
Version-Release number of selected component:
libreport version: 2.0.14
:Thread no. 1 (10 frames)
: #0 read at ../sysdeps/unix/syscall-template.S:82
: #1 _IO_new_file_underflow at fileops.c:619
: #2 _IO_default_uflow at genops.c:440
: #3 _IO_getline_info at iogetline.c:74
: #4 _IO_fgets at iofgets.c:58
: #5 fgets at /usr/include/bits/stdio2.h:255
: #6 xsane_read_pnm_header at ../../src/xsane-save.c:444
: #7 xsane_viewer_read_image_header at ../../src/xsane-viewer.c:2117
: #8 xsane_viewer_new at ../../src/xsane-viewer.c:2871
: #9 xsane_multipage_show_callback at ../../src/xsane-multipage-project.c:801
Created attachment 631934 [details]
Created attachment 631935 [details]
Created attachment 631936 [details]
Created attachment 631937 [details]
Created attachment 631938 [details]
Created attachment 631939 [details]
Created attachment 631940 [details]
Created attachment 631941 [details]
Created attachment 631942 [details]
Created attachment 631943 [details]
Same thing, trying to see a page from a multi-page project. This page was modified by GIMP
OS Release: Fedora release 17 (Beefy Miracle)
XSane's own PNM parser is not very robust and can only read PNM produced by XSane.
(In reply to comment #12)
> XSane's own PNM parser is not very robust and can only read PNM produced by
When a valid PNM file is fed to XSane decoder, the decoder enter in infinite loop mode, trying to find XSane additional (optional) headers.
Created attachment 632076 [details]
Fix XSane PNM decoder
Here's a patch that improve the XSane PNM decoder:
- be sure to read return codes not to enter in infinite loop
- be resilient to malformed or unrecognized PNM file
- report errors in debug mode
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.
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 17'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 17 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, you are encouraged change the
'version' to a later Fedora version prior to Fedora 17's end of life.
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.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.