Re: Permission Problem with xsane - more
On 04/10/11 07:02, Thomas H. George wrote:
> On Mon, Oct 03, 2011 at 02:50:36PM +1100, Scott Ferguson wrote:
>> On 02/10/11 23:30, Thomas H. George wrote:
>>> On Sun, Oct 02, 2011 at 02:49:04PM +1100, Scott Ferguson wrote:
>>>> On 02/10/11 03:25, Thomas H. George wrote:
>>>>> On Thu, Sep 29, 2011 at 04:20:01PM -0400, Thomas H. George wrote:
<snipped>
>>>> <snipped>
>>>>>
>>>>
>>> Epson Perfection 2400 Photo
>>
<snipped>
> Just found the following:
>
>
> Script started on Mon 03 Oct 2011 03:38:15 PM EDT
> tom@dragon:~$ lsusb -s 001:005
> Bus 001 Device 005: ID 04b8:011b Seiko Epson Corp. Perfection 2400 Photo
> tom@dragon:~$ scanimage -L
> device `epson2:libusb:001:005' is a Epson GT-9300 flatbed scanner
> device `epson:libusb:001:005' is a Epson GT-9300 flatbed scanner
> tom@dragon:~$ exit
>
> Script done on Mon 03 Oct 2011 03:39:13 PM EDT
>
> As noted above I have been using scanimage from a terminal for a long
> time. It has always been a little bit quirky. xsane also thinks it is
> using a GT-9300 flatbed scanner. sane-find-scanner finds 0x04b8:0x011b
> at 001:005 but does not report a model name.
Does it normally? I thought is just reported the device name(?)
>
> Could this be my problem?
Well spotted!
Partially - the identification is correct (sane treats both models
identically as they have the same USB ids)
If the label bothers you - after backing it up, edit
/lib/udev/60-libsane.rules:-
# Epson Perfection 2400 | Epson GT-9300UF | Epson Perfection 2400 PHOTO
and replace with
# Epson Perfection 2400 PHOTO
The problem seems to be that *both* epson and epson2 backends are being
called - I could make a couple of (guesses) suggestions on how to
disable one of the backends, but first try just specifying one of the
devices, if you haven't already eg.:-
$ scanimage -d epson2:libusb:001:005
and
$ scanimage -d epson:libusb:001:005
NOTE: you'll probably need to append a "-x n -y n --format=type >
path/filename"
<snipped>
Cheers
Reply to: