the scripts i'm reusing were written ages ago for use with network
attached hp all-in-ones. for this machine i could have gone without
specifying the scanner. i failed to remember that and will make that
change. thanks for pointing it out.
the libusb messages appear anytime scanimage is
I'm not sure why libusb would be so noisy by default. Can you check
your environment vars to see if there is some libusb debugging turned
on?
allan
On Wed, Jun 11, 2014 at 9:17 AM, gobo gobo...@gmail.com wrote:
the scripts i'm reusing were written ages ago for use with network
attached hp
thanks for the reply.
changed my approach and used scanimage -f %d to capture the device
in my script. this works well enough since i have only one scanner.
is there a way to suppress the
libusb couldn't open USB device /dev/bus/usb/001/001: Permission denied.
libusb requires write access to
If you only have one scanner, you don't need to name the device.
Where do you see those libusb error messages?
allan
On Tue, Jun 10, 2014 at 4:57 PM, gobo gobo...@gmail.com wrote:
thanks for the reply.
changed my approach and used scanimage -f %d to capture the device
in my script. this
generally, i know how to write udev rules. but i'm not sure how to
write one for libsane.
scanimage -L returns something like:
device `canon_dr:libusb:001:002' is a CANON DR-2580C scanner
where the 001:002 is always changing. :005, :008, etc.
so in 55-libsane.rules there is:
# Canon DR-2580C
gobo writes:
generally, i know how to write udev rules. but i'm not sure how to
write one for libsane.
scanimage -L returns something like:
device `canon_dr:libusb:001:002' is a CANON DR-2580C scanner
where the 001:002 is always changing. :005, :008, etc.
so in 55-libsane.rules there
