Hi Julian,
Thanks for your reply. I did some more testing, and this problem may
very well be not the libsane's fault. At this point I am not sure where
the problem lies.
Op 26-9-2010 16:16, Julien BLACHE schreef:
Those look like genuine errors, so first check your logs for kernel
messages about your scanner, and if there's nothing there:
There are indeed messages in the kernel logs. I omitted them earlier
because they are related to scanbuttond, which I had shutdown before
testing with scanimage. (scanbuttond used to work in the past, but it
broke a while ago after a libsane update).
These are the kernel messages:
[ 65.732459] usb 3-1: usbfs: USBDEVFS_CONTROL failed cmd scanbuttond
rqt 64 rq 12 len 1 ret -110
[ 75.736306] usb 3-1: usbfs: USBDEVFS_CONTROL failed cmd scanbuttond
rqt 192 rq 12 len 1 ret -110
[ 85.732147] usb 3-1: usbfs: USBDEVFS_CONTROL failed cmd scanbuttond
rqt 64 rq 12 len 1 ret -110
[ 96.197038] usb 3-1: usbfs: USBDEVFS_CONTROL failed cmd scanbuttond
rqt 64 rq 12 len 1 ret -110
[ 106.196888] usb 3-1: usbfs: USBDEVFS_CONTROL failed cmd scanbuttond
rqt 64 rq 12 len 1 ret -110
and also:
[ 5258.573727] usb 3-1: usbfs: USBDEVFS_CONTROL failed cmd
sane-find-scann rqt 128 rq 6 len 2 ret -110
[ 5259.576805] usb 3-1: usbfs: USBDEVFS_CONTROL failed cmd
sane-find-scann rqt 128 rq 6 len 2 ret -110
(sane-find-scanner is called by scanbuttond initialization script)
- check that the scanner does work
The device isn't broken or something like that. It works flawless when
connected to Windows. And it has worked in Linux.
- plug the scanner directly into the machine, unplug any other USB
devices that aren't strictly required
It is plugged in directly, and no other USB devices are connected.
So about the testing I did, I've just powercycled the device (having
scanbuttond stopped), and it directly started working after that.
But after a fresh system boot, the device never works. This seems to be
related to scanbuttond being started at boot.
If I disable the scanbuttond startup, scanimage works after boot.
So, it seems like scanbuttond in the boot process is confusing the USB
layer or the scanner itself. And even if I shutdown scanbuttond after
boot, the scanner is still broken until I reset the device.
Scanbuttond also uses libsane and libusb. So, the question is, who is at
fault here?
Any ideas?
Robbert
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
