Package: libsane Version: 1.0.15-9 Severity: important
-- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.11-rc3 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages libsane depends on: ii adduser 3.51 Add and remove users and groups ii debconf 1.4.25 Debian configuration management sy ii libc6 2.3.2.ds1-21 GNU C Library: Shared libraries an ii libgphoto2-2 2.1.5-4 gphoto2 digital camera library ii libgphoto2-port0 2.1.5-4 gphoto2 digital camera port librar ii libieee1284-3 0.2.8-2 Cross-platform library for paralle ii libjpeg62 6b-9 The Independent JPEG Group's JPEG ii libusb-0.1-4 2:0.1.10a-9 userspace USB programming library ii makedev 2.3.1-78 creates device files in /dev ii sane-utils 1.0.15-9 API library for scanners -- utilit -- no debconf information my epson 1650 photo used to work well about two months ago. It stops working under linux after some updates. The symptoms are: (as root, comments stripped) # sane-find-scanner found USB scanner (vendor=0x04b8 [EPSON], product=0x0110 [EPSON Scanner]) at libusb:002:010 so it somehow does see the scanner. here is what lsusb reports: # lsusb Bus 004 Device 001: ID 0000:0000 Bus 003 Device 001: ID 0000:0000 Bus 002 Device 010: ID 04b8:0110 Seiko Epson Corp. Perfection 1650 Bus 002 Device 001: ID 0000:0000 Bus 001 Device 005: ID 046d:c012 Logitech, Inc. Optical Mouse Bus 001 Device 001: ID 0000:0000 # ls -l /proc/bus/usb/002 total 0 -rw-r--r-- 1 root root 43 2005-05-07 20:54 001 -rw-rw---- 1 root scanner 50 2005-05-07 20:54 010 so hotplug also recognized it and changed the permissions of the device. Here is the config file of the epson backend # epson.conf # # here are some examples for how to configure the EPSON backend # # SCSI scanner: # scsi EPSON # # Parallel port scanner: #pio 0x278 #pio 0x378 #pio 0x3BC # # USB scanner: # There are two different methods of configuring a USB scanner: libusb and the kernel module # For any system with libusb support (which is pretty much any recent Linux distribution) the # following line is sufficient. This however assumes that the connected scanner (or to be more # accurate, it's device ID) is known to the backend. # For libusb support for unknown scanners use the following command # usb <product ID> <device ID> # e.g.: # usb 0x4b8 0x110 # And for the scanner module, use the following configuration: #usb /dev/usbscanner0 #usb /dev/usb/scanner0 usb ---------------------------------------------------------------------- but scanimage -L (under root as well as under normal user in group scanner) reports: 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). The Light on the scanner shortly blinks when I issue the command, then the command hangs for a while and finally issues an error message. Here is the output of $ USB_DEBUG=255 scanimage -L usb_set_debug: Setting debugging level to 255 (on) usb_os_init: Found USB VFS at /proc/bus/usb usb_os_find_busses: Found 004 usb_os_find_busses: Found 003 usb_os_find_busses: Found 002 usb_os_find_busses: Found 001 usb_os_find_busses: Skipping non bus directory devices usb_os_find_devices: couldn't get connect info usb_os_find_devices: Found 001 on 004 error obtaining child information: Operation not permitted usb_os_find_devices: couldn't get connect info usb_os_find_devices: Found 001 on 003 error obtaining child information: Operation not permitted usb_os_find_devices: Found 010 on 002 usb_os_find_devices: couldn't get connect info usb_os_find_devices: Found 001 on 002 error obtaining child information: Inappropriate ioctl for device error obtaining child information: Operation not permitted usb_os_find_devices: couldn't get connect info usb_os_find_devices: Found 005 on 001 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: couldn't get connect info usb_os_find_devices: Found 001 on 001 error obtaining child information: Operation not permitted error obtaining child information: Operation not permitted USB error: error submitting URB: No such file or directory [ pause of approx 5 seconds] USB error: error submitting URB: No such file or directory USB error: error submitting URB: No such file or directory No scanners were identified. If you were expecting something different, ... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
