Red Hat Bugzilla – Bug 1297169
sane-backends 1.0.25 regresses support for Fujitsu ScanSnap ix500
Last modified: 2016-07-31 23:23:30 EDT
Description of problem
With 1.0.25, my ScanSnap ix500 is no longer being able to scan anything. The device shows up in `scanimage -L` but an actual scan fails and the device subsequently disappears from `scanimage -L` until unplugging and plugging its USB cable.
Version-Release number of selected component (if applicable): 1.0.25
How reproducible: every time
Steps to Reproduce:
1. Install sane-backends-1.0.25
2. SANE_DEBUG_FUJITSU=255 scanimage -d "fujitsu:ScanSnap iX500:14767" --resolution 50 >foo.pnm 2>foo.log
3. Observe the scanner not even beginning to scan and the resulting empty output image (logs attached)
scanimage is unable to scan anything from this device.
A page is scanned, as with 1.0.24 (logs attached).
I've attached debug info from both 1.0.24 and 1.0.25. 1.0.25
Created attachment 1113239 [details]
Logs of a successful scan
Created attachment 1113240 [details]
Logs of a failed scan
(In reply to Delyan Kratunov from comment #0)
> Description of problem
> With 1.0.25, my ScanSnap ix500 is no longer being able to scan anything. The
> device shows up in `scanimage -L` but an actual scan fails and the device
> subsequently disappears from `scanimage -L` until unplugging and plugging
> its USB cable.
No wonder, it doesn't reply anymore. See the bottom of the "failed" log which has a couple of repetitions of these:
--- 8< ---
[fujitsu] do_usb_cmd: start
[fujitsu] cmd: writing 31 bytes, timeout 500
[fujitsu] cmd: >>
[fujitsu] 000: 43 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 C...............
[fujitsu] 010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ...............
[fujitsu] cmd: wrote 31 bytes, retVal 0
[fujitsu] stat: reading 13 bytes, timeout 500
[fujitsu] stat: <<
[fujitsu] stat: read 0 bytes, retVal 9
[fujitsu] stat: return error 'Error during device I/O'
[fujitsu] WARNING: Brain-dead scanner. Hitting with stick
--- >8 --
The log before that is almost identical (virtually identical as far as communication between the computer and the scanner are concerned). Did anything else than the version of sane-backends change on the system, e.g. the kernel?
> Did anything else than the version of sane-backends change on the system, e.g. the kernel?
Nope. This is entirely reproducible by just updating/downgrading sane-backends-* between 1.0.24 and 1.0.25.
Hmm, there's nothing in the logs that indicates that the fujitsu backend driver does things differently in 1.0.25. Would you please regenerate the logs with sanei_usb debugging enabled additionally? I.e.:
SANE_DEBUG_FUJITSU=255 SANE_DEBUG_SANEI_USB=255 scanimage -d "fujitsu:ScanSnap iX500:14767" --resolution 50 >foo.pnm 2>foo.log
Created attachment 1119710 [details]
Successful scan .24 + usb
Created attachment 1119711 [details]
Failed scan .25 + usb
If you run `diff --side-by-side --width 160 foo.24.log foo.25.log | less`, you'll immediately see that the failure is at 13 byte read early on. It succeeds in .24 and fails in .25.
Could this be related to the fact that custom Fedora usb patches were removed in .25? This is over a usb3 port as well, if that matters.
Any news on this? Can we at least mark this bug as confirmed?
Delyan, sorry for dropping the ball. We don't have a "CONFIRMED" state, but I'll move this to ASSIGNED which is kind of our equivalent.
I've seen that there are a couple of changes in the USB code after 1.0.25 was released, can you build the current development version of sane-backends from source and try whether it makes a difference to you?
I have a new machine with Fedora 32x64 with a Gigabyte Z170-D3H main board with rear panel usb-3 connectors and front panel usb-2 connectors. I have an HP-7400c scanner.
with the scanner in the usb-3 port
Bus 001 Device 069: ID 03f0:0801 Hewlett-Packard ScanJet 7400c
but sane reports no scanner available
with the scanner in the usb-2 port
Bus 001 Device 070: ID 03f0:0801 Hewlett-Packard ScanJet 7400c
sane finds the scanner and works
Steve, this is is a different issue (different symptoms and scanner model). That it works on a USB2 port but doesn't on a USB3 port indicates some problem in the USB3 kernel driver (i.e. outside of sane-backends). Please file a separate bug report against the kernel component. Thanks!
Nils, 1.0.25-2.fc24 seems to work just fine with the ScanSnap ix500. Closing as resolved