You are not logged in.
Ok, I've seen this problem on other distros too, so Arch must have something in common with them, but I'm on Arch right now, so I'll try my luck here.
I have a Fujitsu USB scanner, sane installed, udev scanner rules file installed. My user is in the scanner and wheel groups.
lsusb finds it fine: Bus 004 Device 010: ID 04c5:10cf Fujitsu, Ltd
USB device looks right: crw-rw-r--+ 1 root scanner 189, 392 Oct 9 15:33 ./bus/usb/004/010
sane-find-scanner finds it fine: found USB scanner (vendor=0x04c5, product=0x10cf) at libusb:004:010
"scanimage -L" works just fine the first time: device `fujitsu:libusb:004:010' is a FUJITSU fi-4340Cd scanner
But only that time, then it fails to find one. If I strace the scanimage binary, it shows me where it's failing: ioctl(12, USBDEVFS_SETCONFIGURATION, 0x7fff94199eac) = -1 ETIMEDOUT (Connection timed out)
When it works the first time, that line of the strace output looks like this: ioctl(12, USBDEVFS_SETCONFIGURATION, 0x7fffc564cb3c) = 0
I even tried compiling libusb 1.0 into /opt/libusb and pointed sane at it, but same problem. I'm starting to think it's a kernel problem.
Ideas?
Offline
BTW, this is on a fresh install of Arch done yesterday: Linux groovy9 3.11.4-1-ARCH #1 SMP PREEMPT Sat Oct 5 21:22:51 CEST 2013 x86_64 GNU/Linux
For a plan B, if there's a straightforward way to custom compile my own kernel, I'd like to try a slightly older one to see if I have better luck. This same model of scanner is working fine on a 3.5 kernel, for example.
Last edited by groovy9 (2013-10-09 21:34:22)
Offline
Update: Same problem on Kernel 3.4.65.
Offline
Update: problem solved. It's a bug in the SANE backend that only bites on my specific scanner with a recent libusb.
Offline