[Slackbuilds-users] Pixma driver module for Canon scanner

[Rich Shepard]

On Sat, 11 Jan 2020, Christoph Willing wrote:

> Since your device is fairly new, I wonder if it will be recognised by just
> adding an entry for it, along with the others, in
> /etc/sane.d/genesys.conf - something like:
>
> # Canon LiDE 400
> usb 0x04a9 0x1912

Chris,

Done. scanimage -L still cannot find any scanner

> If it doesn't work in genesys.conf (I just suggest that first because all
> the other LiDE's are in there), then you could try putting it in
> /etc/sane.d/pixma.conf, although that seems set up for networked devices
> rather than USB.

This did nothing. It didn't like the domain name, or localhost, and I tried
a couple of different host names such as 'canon' and 'LiDE400'.

sane-find-scanner seems to check all USB ports:

could not open USB device 0x1d6b/0x0003 at 006:001: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0002 at 005:001: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0003 at 004:001: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0002 at 003:001: Access denied (insufficient permissions)
could not open USB device 0x174c/0x55aa at 002:005: Access denied (insufficient permissions)
could not open USB device 0x05e3/0x0616 at 002:008: Access denied (insufficient permissions)
could not open USB device 0x05e3/0x0612 at 002:002: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0003 at 002:001: Access denied (insufficient permissions)
could not open USB device 0x047d/0x2048 at 001:004: Access denied (insufficient permissions)
could not open USB device 0x05e3/0x0610 at 001:045: Access denied (insufficient permissions)
could not open USB device 0x05e3/0x0610 at 001:002: Access denied (insufficient permissions)
found USB scanner (vendor=0x04a9 [Canon], product=0x1912 [LiDE 400]) at libusb:001:048
could not open USB device 0x1d6b/0x0002 at 001:001: Access denied (insufficient permissions)
   # Your USB scanner was (probably) detected. It may or may not be supported by
   # SANE. Try scanimage -L and read the backend's manpage.

Thanks,

Rich