Your message dated Sun, 28 Aug 2005 17:07:20 +0200
with message-id <[EMAIL PROTECTED]>
and subject line #308081: epson scanners problems probably fixed by latest
libsane-extras
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 7 May 2005 19:02:35 +0000
>From [EMAIL PROTECTED] Sat May 07 12:02:35 2005
Return-path: <[EMAIL PROTECTED]>
Received: from smtp06.web.de [217.72.192.224]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DUUZO-00085g-00; Sat, 07 May 2005 12:02:35 -0700
Received: from [217.2.57.20] (helo=nilux.augustus.priv)
by smtp06.web.de with asmtp (TLSv1:DES-CBC3-SHA:168)
(WEB.DE 4.105 #282)
id 1DUUYp-00083D-00; Sat, 07 May 2005 21:01:59 +0200
Received: from nils by nilux.augustus.priv with local (Exim 4.43)
id 1DUUYr-0007lC-Po; Sat, 07 May 2005 21:02:01 +0200
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Nils Rennebarth <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: libsane: epson backend stops working in newer version
X-Mailer: reportbug 3.11
Date: Sat, 07 May 2005 21:02:01 +0200
Message-Id: <[EMAIL PROTECTED]>
Sender: [EMAIL PROTECTED]
X-Sender: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
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,
...
---------------------------------------
Received: (at 308081-done) by bugs.debian.org; 28 Aug 2005 15:08:52 +0000
>From [EMAIL PROTECTED] Sun Aug 28 08:08:52 2005
Return-path: <[EMAIL PROTECTED]>
Received: from frigate.technologeek.org [62.4.21.148] (postfix)
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1E9OmC-0006mj-00; Sun, 28 Aug 2005 08:08:52 -0700
Received: by frigate.technologeek.org (Postfix, from userid 1000)
id 8D8331474331; Sun, 28 Aug 2005 17:07:20 +0200 (CEST)
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: #308081: epson scanners problems probably fixed by latest
libsane-extras
From: Julien BLACHE <[EMAIL PROTECTED]>
Date: Sun, 28 Aug 2005 17:07:20 +0200
Message-ID: <[EMAIL PROTECTED]>
User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4 (Jumbo Shrimp, linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no
version=2.60-bugs.debian.org_2005_01_02
Version: 1.0.16.3
Hi,
I believe this problem was caused by a bug in the epkowa backend,
which I fixed in libsane-extras 1.0.16.3.
I am closing this bug; if the problem is not fixed by libsane-extras
1.0.16.3 nor by libsane 1.0.16-1, please reopen with details.
Thanks,
JB.
--
Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]>
Public key available on <http://www.jblache.org> - KeyID: F5D6 5169
GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
