[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On Mon, 2007-10-08 at 11:55 +0100, Robin Cornelius wrote: > Sounds like a call from sane or one of one of the sane libs. I had opened xsane which started scanning for devices and came up with the message. > > Do you have permissions to open the USB device, scanners seem to be a > slight pain as the udev rules are not always set for the required USB > ID to give user (not root) access. > > Try "sane-find-scanner"and "scanimage -L" to see if sane knows about > your scanner (as root), if you can get the sane tools playing as root > then get them working as normal user. I get "command not found" > > man sane, man sane-find-scanner, I get "no manual entry for "sane-find-scanner" > man scanimage may be of help ditto I installed sane-utils and the commands worked. It identifies the scanner correctly. I then get the same error as before on loading xsane. using scanimage (not root) I get "[snapscan] cannot open firmware file /usr/share/sane/snapscan/your-firmwarefile.bin" "[snapscan] Edit the firmware file in snapscan.conf "scanimage: open of device snapscan:libusb:001.004 failed: Invalid argument" (I used a different usb port) How do I edit the .conf file? Thanks very much. Bigger steps on the command line! -- james kilty http://www.kilty.demon.co.uk -- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/linux_adm/list-faq.html