On Sun, 2006-07-30 at 22:51 +1200, Nick Rout wrote: > > All of those scanning options except iscan use sane as the base. I would be > using the sane command line tools and looking for errors in their output and > in the system logs. > > scanimage -L > > and > > sane-find-scanner > > come to mind.
Ta, Nick, but I already had the command-line tools and had tried those commands. (The output perhaps got lost in my over-length message.) Trying them again: sane-find-scanner yields found USB scanner (vendor=0x04b8 [EPSON], product=0x0112 [EPSON Scanner]) at libusb:004:005 scanimage -L yields device `epson:libusb:004:005' is a Epson GT-9700 flatbed scanner (makes sense - I've powered the scanner off and on a few times, and each cycle increments the file number in /proc/bus/usb/004/ by one) scanimage -v -v yields scanimage: sane_start: Error during device I/O scanimage: read 0 bytes in total Closing device Calling sane_exit scanimage: finished Xsane doesn't seem to have a debug mode. I've tried iscan --debug but can't suss out where the output's gone. None of the log files in /var/log contain anything that seems apropos. The permissions for /proc/bus/usb/004/<scanner> are set to 644 when I restart the scanner, but running as root does NOT change the problem, nor does resetting the permissions. I don't want to have to reboot into either Windows or Knoppix each time I need to run the scanner. =====Andrew
