Created attachment 316195 [details] DMESG There were some similar bugs but all of them seems to be fixed in earlier versions. However, now, after upgrade I stuck with scanimage -L doean't see my scanner. From the beginning: k7 ~ # lsusb ... Bus 001 Device 003: ID 04b8:012e Seiko Epson Corp. GT-F670 [Perfection V200 Photo] ... k7 ~ # sane-find-scanner ... found USB scanner (vendor=0x04b8 [EPSON], product=0x012e [EPSON Scanner]) at libusb:001:003 ... k7 ~ # scanimage -L No scanners were identified. ... strace log of scanimage is attached. Interesting is the following: 22356 open("/dev/bus/usb/001/003", O_RDWR) = 3 22356 ioctl(3, SNDRV_CTL_IOCTL_ELEM_READ or USBDEVFS_IOCTL or USBDEVFS_IOCTL32, 0x7fffec2842e0) = -1 ENOTTY (Inappropriate ioctl for device) If I add the following line to /etc/sane.d/epkowa.conf: usb 0x04b8 0x012e then I get repeatedly in strace scanimage -L: select(4, NULL, [], NULL, {0, 1000}) = 0 (Timeout) ioctl(3, USBDEVFS_REAPURBNDELAY or USBDEVFS_REAPURBNDELAY32, 0x7fff9b840468) = -1 EAGAIN (Resource temporarily unavailable) To me looks like bug in epkowa backend (iscan) or in libusb. However I had no problems with iscan 2.26.2 before upgrade. I tryed different combinations with downgrading iscan, iscan-data, libusb, sane-backends but with no luck. Problem detected on kernel 2.6.37. No I upgraded to 3.4.3 and it also didn't help. Currently I have the following versions of the programs: media-gfx/iscan-2.28.1.3 media-gfx/iscan-data-1.13.0.1 media-gfx/sane-backends-1.0.22-r2 dev-libs/libusb-1.0.9 Need to say, that I made a small tweak to iscan to compile with new libpng-1.5.x. However I don't beleive it has any impact on this problem.
Created attachment 316197 [details] strace scanimage -L
Created attachment 316199 [details] strace scanimage-L with added usb 0x04b8 0x012e to epkowa.conf
Created attachment 316201 [details] emerge info
Sorry, I have absolutely no idea what is going wrong here.
Maybe I can do additional tests or provide additional logs that can help? Please let me know.
CC-ing iscan maintainer. You could try if the -v option gives helpful output, or run scanimage with the -A option to check if that backend offers any debugging switches. Good luck!
Also try with 1.0.23