Bug 1104079

Summary: [abrt] simple-scan: _IO_fread(): simple-scan killed by SIGSEGV
Product: [Fedora] Fedora Reporter: tobias.weise
Component: simple-scanAssignee: David King <amigadave>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: amigadave, ignatenko, negativo17, tobias.weise
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/2a2f774f7f4aa798a7b157f797ca477c5fe1070a
Whiteboard: abrt_hash:2173a2d2549bb736c878e32347a4de4ba81a2640
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-30 01:02:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description tobias.weise 2014-06-03 09:00:52 UTC
Description of problem:
Simple Scan crashed while scanning a two-sided document using a HP Scanjet 8270's automatic document feed. It scanned the front side correctly, but crashed while scanning the back side.

Version-Release number of selected component:
simple-scan-3.10.3-1.fc20

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        simple-scan
crash_function: _IO_fread
executable:     /usr/bin/simple-scan
kernel:         3.14.4-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (4 frames)
 #0 _IO_fread at iofread.c:41
 #1 fread at /usr/include/bits/stdio2.h:295
 #2 reader_process at avision.c:7001
 #3 local_thread at sanei_thread.c:355

Comment 1 tobias.weise 2014-06-03 09:00:57 UTC
Created attachment 901677 [details]
File: backtrace

Comment 2 tobias.weise 2014-06-03 09:00:59 UTC
Created attachment 901678 [details]
File: cgroup

Comment 3 tobias.weise 2014-06-03 09:01:02 UTC
Created attachment 901679 [details]
File: core_backtrace

Comment 4 tobias.weise 2014-06-03 09:01:04 UTC
Created attachment 901680 [details]
File: dso_list

Comment 5 tobias.weise 2014-06-03 09:01:07 UTC
Created attachment 901681 [details]
File: environ

Comment 6 tobias.weise 2014-06-03 09:01:09 UTC
Created attachment 901682 [details]
File: exploitable

Comment 7 tobias.weise 2014-06-03 09:01:11 UTC
Created attachment 901683 [details]
File: limits

Comment 8 tobias.weise 2014-06-03 09:01:13 UTC
Created attachment 901684 [details]
File: maps

Comment 9 tobias.weise 2014-06-03 09:01:16 UTC
Created attachment 901685 [details]
File: open_fds

Comment 10 tobias.weise 2014-06-03 09:01:18 UTC
Created attachment 901686 [details]
File: proc_pid_status

Comment 11 tobias.weise 2014-06-03 09:01:20 UTC
Created attachment 901687 [details]
File: var_log_messages

Comment 12 David King 2014-06-04 16:00:11 UTC
This sort of crash generally indicates a problem with the SANE backend. Is the crash reproducible? If so, can you try scanning with XSane and report if that works or crashes?

Comment 13 tobias.weise 2014-06-04 20:05:19 UTC
Hey there, 

yes, the crach is reproducible and it always happens when scanning the back side of a document from the ADF. XSane does not crash, but fails to safe / recognize the back side and only safes the front of the page (when scanning to multi-page project).

Any more info needed?

Comment 14 David King 2014-06-04 20:29:58 UTC
I filed an upstream bug in Launchpad:

https://bugs.launchpad.net/fedora/+bug/1326519

Could you attach the debug output from running Simple Scan (and triggering there crash) in a terminal there:

simple-scan --debug > simple-scan.log 2>&1

Comment 15 tobias.weise 2014-06-04 21:25:50 UTC
Thanks, will do this in a second.

Comment 16 Fedora End Of Life 2015-05-29 12:00:49 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 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 this bug is closed as described in the policy above.

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.

Comment 17 Fedora End Of Life 2015-06-30 01:02:19 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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