Yeah, you can remove the symlink (if the above command is the
one you issued, the symlink is /dev/usbscanner) with:
I don't think that's the problem, but it's certainly worth a shot, and
I'd be happy to be wrong.

I'm getting both /dev/usbscanner and /dev/usb/scanner0 reported in xsane when I start it, either one works if I select it. What version of xsane are you using and did you install it from rpm?

Hullo again,

I've managed to work-out how to break the symlink causing the above double device report-back.

code: sane-find-scanner now shows just the one :

found usb scanner (vendor=0x04a9, product=0x2204) at device/dev/usb/scanner0

Still not having any joy with either the xsane or scanimage commands. Still getting the: 'Failed to start scanner, Device busy' messages.

Any further suggestions would be most appreciated.

Regards,
tonyath

Hi Aussie,

I have both xsane & xsane-gimp installed. Both are version 0.87-1mdk.

Yes, these were both installed from rpm.

Regards,

Uninstall the xsane rpm's and try the source.

Thanks,

I'll let you know how it goes.

Hello

I was also having a very similar problem and have happened onto a cheap hack to fix it.

- Start xsane
- Hitting scan / preview will now cause the "Device Busy" error.
- Cycle the power on the scanner.
- Now hitting the scan / preview buttons does not do much of anything but the "Device Busy" no longer appears.
- Without closing xsane run scanimage -d ... (just like before)
- Ctrl-C the scanimage once the scanner starts going.
- This should now leave you with a working instance of xsane.

You have to do this everytime you restart xsane.

same problem here I/O error with an UT12 plustek, runnning arch linux [kernel 2.4.25], sane from source

#xsane plustek:/dev/usb/scanner0

reports an I/O error, no pulse from scanner
even though
#sane-find-scanner
does find it

also I've
#modprobe scanner
and usb-storage is lsmod active