Crashes when power cycling scanner in between scans

[David King]

I maintain the Simple Scan package in Fedora and a user has filed a bug report about a crash. From the downstream bug report:

Scanned, turned scanner off and on, scanned again -- got crash. Executing the scenario in XSane i got: "Failed to start scanner: Error during device I/O" [but no crash].

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

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

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 libusb_clear_halt at core.c:1584
 #1 sanei_usb_clear_halt at sanei_usb.c:2203
 #2 usb_dev_close at xerox_mfp-usb.c:95
 #3 sane_dll_close at dll.c:1223
 #4 sane_close at dll-s.c:78
 #5 scanner_close_device at /home/bob/bzr/simple-scan/3.10/src/scanner.vala:766
 #6 scanner_fail_scan at /home/bob/bzr/simple-scan/3.10/src/scanner.vala:780
 #7 scanner_do_get_parameters at /home/bob/bzr/simple-scan/3.10/src/scanner.vala:1230
 #8 scanner_scan_thread at /home/bob/bzr/simple-scan/3.10/src/scanner.vala:1481
 #9 _scanner_scan_thread_gthread_func at scanner.c:12474

[Michal (michal-redhat-bugs)]

Description of problem:
Scanned, turned scanner off and on, scanned again -- got crash

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

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

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 libusb_clear_halt at core.c:1584
 #1 sanei_usb_clear_halt at sanei_usb.c:2203
 #2 usb_dev_close at xerox_mfp-usb.c:95
 #3 sane_dll_close at dll.c:1223
 #4 sane_close at dll-s.c:78
 #5 scanner_close_device at /home/bob/bzr/simple-scan/3.10/src/scanner.vala:766
 #6 scanner_fail_scan at /home/bob/bzr/simple-scan/3.10/src/scanner.vala:780
 #7 scanner_do_get_parameters at /home/bob/bzr/simple-scan/3.10/src/scanner.vala:1230
 #8 scanner_scan_thread at /home/bob/bzr/simple-scan/3.10/src/scanner.vala:1481
 #9 _scanner_scan_thread_gthread_func at scanner.c:12474

[Michal (michal-redhat-bugs)]

Created attachment 877241
File: backtrace

[Michal (michal-redhat-bugs)]

Created attachment 877242
File: cgroup

[Michal (michal-redhat-bugs)]

Created attachment 877243
File: core_backtrace

[Michal (michal-redhat-bugs)]

Created attachment 877244
File: dso_list

[Michal (michal-redhat-bugs)]

Created attachment 877245
File: environ

[Michal (michal-redhat-bugs)]

Created attachment 877246
File: exploitable

[Michal (michal-redhat-bugs)]

Created attachment 877247
File: limits

[Michal (michal-redhat-bugs)]

Created attachment 877248
File: maps

[Michal (michal-redhat-bugs)]

Created attachment 877249
File: open_fds

[Michal (michal-redhat-bugs)]

Created attachment 877250
File: proc_pid_status

[Michal (michal-redhat-bugs)]

Created attachment 877251
File: var_log_messages

[David (david-redhat-bugs)]

This seems like a crash in the SANE backend and not Simple Scan. Can you reproduce the crash with xsane and report back?

[Michal (michal-redhat-bugs)]

Negative. Executing the scenario in XSane i got: "Failed to start scanner: Error during device I/O".

dmesg:

[18729.559996] usb 2-1.3.1: new high-speed USB device number 11 using ehci-pci
[18729.646699] usb 2-1.3.1: New USB device found, idVendor=04e8, idProduct=3441
[18729.646705] usb 2-1.3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[18729.646708] usb 2-1.3.1: Product: SCX-3200 Series
[18729.646710] usb 2-1.3.1: Manufacturer: Samsung Electronics Co., Ltd.
[18729.646712] usb 2-1.3.1: SerialNumber: Z5EXBFEB403272K
[18729.648153] usblp 2-1.3.1:1.1: usblp0: USB Bidirectional printer dev 11 if 1 alt 0 proto 2 vid 0x04E8 pid 0x3441
[18730.734715] usblp0: removed
[18730.736126] usblp 2-1.3.1:1.1: usblp0: USB Bidirectional printer dev 11 if 1 alt 0 proto 2 vid 0x04E8 pid 0x3441
[18750.423953] usb 2-1.3.1: usbfs: interface 1 claimed by usblp while 'xsane' sets config #1
[18754.476759] usb 2-1.3.1: usbfs: interface 1 claimed by usblp while 'xsane' sets config #1
[18785.674316] usb 2-1.3.1: USB disconnect, device number 11
[18785.674652] usblp0: removed
[18793.526859] usb 2-1.3.1: new high-speed USB device number 12 using ehci-pci
[18793.613493] usb 2-1.3.1: New USB device found, idVendor=04e8, idProduct=3441
[18793.613500] usb 2-1.3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[18793.613503] usb 2-1.3.1: Product: SCX-3200 Series
[18793.613506] usb 2-1.3.1: Manufacturer: Samsung Electronics Co., Ltd.
[18793.613508] usb 2-1.3.1: SerialNumber: Z5EXBFEB403272K
[18793.614676] usblp 2-1.3.1:1.1: usblp0: USB Bidirectional printer dev 12 if 1 alt 0 proto 2 vid 0x04E8 pid 0x3441
[18794.656155] usblp0: removed
[18794.657370] usblp 2-1.3.1:1.1: usblp0: USB Bidirectional printer dev 12 if 1 alt 0 proto 2 vid 0x04E8 pid 0x3441

[David (david-redhat-bugs)]

Thanks for the quick response. I guess that Simple Scan keeps the device open longer than it should, and have filed a bug upstream:

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

Can you fill in any missing details, including the full name of the scanner and the debug output (by running "simple-scan --debug > simple-scan.log 2>&1")?

[Michal Nowak (michal-nowak-b)]

$ simple-scan --debug > simple-scan.log 2>&1
Segmentation fault (core dumped)

[Fedora (fedora-redhat-bugs)]

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 (fedora-redhat-bugs)]

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.