sane-find-scanner finds it, scanimage -L does not

[Wybo Dekker]

Marius Gedminas wrote:
> On Wed, May 13, 2009 at 02:55:15PM +0200, Wybo Dekker wrote:
>> I have an Epson Perfection V350 scanner and two machines with jaunty:
>> - an HP-Compaq, where the scanner works flawlessly, and
>> - a NEC, where sane-find-scanner finds it, but scanimage -L does not.
>>
>> The relevant files on both machines are the same:
>> - /etc/sane.d/dll.conf (completely commented out)
>> - /etc/sane.d/epkowa.conf (with usb 0x04b8 0x012f, pointing directly to
>>    the scanner)
>> - /etc/sane.d/dll.d/hplib (completely commented out)
>> - /etc/sane.d/dll.d/libsane-extras (commented out, except for epkowa)
>> - /etc/udev/rules.d/45-libsane.rules (was absent on the NEC, copied it
>>    from the compaq)
> 
> Some scanners also need a firmware file in /usr/share/sane/, you may
> want to check whether the contents of that directory are the same on
> both machines.

those directories, and their subdirectories, are completely identical too

>> sane-find-scanner says, on both machines:
>> found USB scanner (vendor=0x04b8 [EPSON], product=0x012f [EPSON 
>> Scanner]) at libusb:001:003
>>
>> scanimage -L says on the Compaq:
>> device `epkowa:libusb:001:003' is a Epson Perfection V350 flatbed scanner
>>
>> but on the NEC:
>> No scanners were identified. If you were expecting something different,
>> check that the scanner is plugged in, turned on and detected by the
>> sane-find-scanner tool (if appropriate). Please read the documentation
>> which came with this software (README, FAQ, manpages).
> 
> My first instinct (having been burned before, once) would be to check
> the permissions of that device.  The first step would be to see if
> 
>    sudo scanimage -L
> 
> finds the scanner on the NEC.  If so, you have a permission problem.

I should have noted that I did everything as root already, so there 
should not be a permission problem (yet...).

> Ubuntu handles scanner permissions via ConsoleKit by setting filesystem
> ACLs on the relevant USB devices.  Check whether
> 
>   getfacl /dev/bus/usb/001/003
> 
> shows that your user has access to the USB device.  Check whether
> ck-list-sessions sees your login session.  Check whether logging out and
> logging in fixes the problem.
> 
> HTH,
> Marius Gedminas
> 

-- 
Wybo