hello to all,

this is not about root to operate scanner, is about scanner port
detection, just thought that it would be ok to post it here.

I'm running hardy amd64 with last upgrades/updates installed
 
uname -r
2.6.24-18-generic

. the scanner used to work ok with previous version 14, 16. didn't use
it for a while; now I'm getting

error  failed to open device 'snapscan:libusb:002:010':invalid argument

and  this

lsusb

Bus 002 Device 010: ID 06bd:208f AGFA-Gevaert NV SnapScan e50
Bus 002 Device 007: ID 0d8d:0105 Promotion & Display Technology, Ltd 
Bus 002 Device 004: ID 0ace:1215 ZyDAS WLA-54L WiFi
Bus 002 Device 003: ID 050d:0224 Belkin Components F5U224 USB 2.0 4-Port Hub
Bus 002 Device 001: ID 0000:0000  
Bus 001 Device 010: ID 050d:0980 Belkin Components 
Bus 001 Device 009: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
Bus 001 Device 008: ID 0451:1446 Texas Instruments, Inc. TUSB2040/2070 Hub
Bus 001 Device 001: ID 0000:0000  

and this

scanimage -L
device `snapscan:libusb:002:010' is a AGFA SNAPSCAN flatbed scanner

and this

sane-find-scanner

  # sane-find-scanner will now attempt to detect your scanner. If the
  # result is different from what you expected, first make sure your
  # scanner is powered up and properly connected to your computer.

  # No SCSI scanners found. If you expected something different, make sure that
  # you have loaded a kernel SCSI driver for your SCSI adapter.

found USB scanner (vendor=0x06bd [AGFA ], product=0x208f [SNAPSCAN]) at 
libusb:002:009
found USB scanner (vendor=0x0ace, product=0x1215) at libusb:002:004
found USB scanner (vendor=0x067b, product=0x2303) at libusb:001:009

pls notice the diff --> 009 on last command output vs before last
command 010  and the error message.

is there any fix to this or at least why it happens.

any help is appreciated.

best regards,
peter b

-- 
[Hardy]Xsane needs root to operate scanner
https://bugs.launchpad.net/bugs/205496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to