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
Created attachment 901677 [details] File: backtrace
Created attachment 901678 [details] File: cgroup
Created attachment 901679 [details] File: core_backtrace
Created attachment 901680 [details] File: dso_list
Created attachment 901681 [details] File: environ
Created attachment 901682 [details] File: exploitable
Created attachment 901683 [details] File: limits
Created attachment 901684 [details] File: maps
Created attachment 901685 [details] File: open_fds
Created attachment 901686 [details] File: proc_pid_status
Created attachment 901687 [details] File: var_log_messages
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?
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?
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
Thanks, will do this in a second.
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.
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.