Your message dated Fri, 11 Feb 2005 01:34:41 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#294667: libusb-0.1-4: Libusb-0.1-4 v1:0.1.9-2 Will not
read data properly from USB Scanners, corrupts output.
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; 11 Feb 2005 00:11:14 +0000
>From [EMAIL PROTECTED] Thu Feb 10 16:11:14 2005
Return-path: <[EMAIL PROTECTED]>
Received: from 91.64-26.246.80.66.in-addr.arpa (knight.gregfolkert.net)
[66.80.246.91]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CzOOw-0003b9-00; Thu, 10 Feb 2005 16:11:14 -0800
Received: from c-67-161-236-108.client.comcast.net ([67.161.236.108]
helo=duke.gregfolkert.net)
by knight.gregfolkert.net with esmtp (Exim 4.34)
id 1CzOOQ-0003R4-Fp; Thu, 10 Feb 2005 19:10:42 -0500
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Greg Folkert <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: libusb-0.1-4: Libusb-0.1-4 v1:0.1.9-2 Will not read data properly from
USB
Scanners, corrupts output.
Bcc: Greg Folkert <[EMAIL PROTECTED]>
X-Mailer: reportbug 3.7.1
Date: Thu, 10 Feb 2005 19:10:40 -0500
Message-ID: <[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: libusb-0.1-4
Version: 1:0.1.9-2
Severity: grave
Justification: renders package unusable
This package renders nearly any device access with libusb impossible. Things
are being griped about on D-D and D-U.
I have back rev'd to the Sarge version and everything Works Honky Dory.
-- System Information:
Debian Release: 3.1
APT prefers experimental
APT policy: (990, 'experimental'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-1-k7
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages libusb-0.1-4 depends on:
ii debconf [debconf-2.0] 1.4.45 Debian configuration management sy
ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an
-- debconf information:
libusb-0.1-4/usbdevfs:
libusb-0.1-4/usbfs-2.4:
libusb-0.1-4/usbfs-2.6:
libusb-0.1-4/nousb:
libusb-0.1-4/usbfs:
I have posted a message to D-U on this matter, on Feb 10, 2005 at 19:08 GMT
-0500 with the text pasted below:
On Thu, 2005-02-10 at 12:00 +0000, Anthony Campbell wrote:
> On 09 Feb 2005, Andreas Rippl wrote:
> > On Tue, Feb 08, 2005 at 11:29:47AM +0000, Anthony Campbell wrote:
> > > xsane has been working well here for many months with my Epson
> > > Perfection 1650. Following a recent upgrade via Sid it now crashes.
> > >
> > > In detail, it initially recognizes the scanner and starts to scan but
> > > then hangs. I therefore kill the running xsane and try again. Now it
> > > says it can't find the scanner. However, if I unplug the scanner and
> > > replug it (Google suggestion), we sometimes get back to the starting
> > > point but again it locks up.
> > >
> > > Results of sane-find-scanner:
> > >
> > > "found USB scanner (vendor=0x04b8, product=0x0110) at libusb:001:006"
> > >
> > > Contents of /etc/sane.d/epson.conf:
> > > --------------------------
> > > # 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 - only enable this if you have an EPSON scanner. It could
> > > # otherwise block your non-EPSON scanner from being
> > > # recognized.
> > > # Depending on your distribution, you may need either the
> > > # first or the second entry.
> > > usb
> > > #usb /dev/usbscanner0
> > > usb /dev/usb/scanner0
> > > usb 0x4b8 0x110
> > > --------------------------------------------
> > >
> > > This is with Debian kernel 2.6.10-1-686 #1
> > >
> > > I've reported this as a bug. Any suggestions?
> > >
> > > Anthony
> > >
> > Hi Anthony,
> >
> > I had a similar problem with a another USB scanner, and for me it helped
> > to remove the 'usb /dev/usb/scanner0' line (from hp.conf in my case),
> > as this is used used for the kernel module. As you use libusb however,
> > you don't need it, but only the line below (usb 0x4b8 0x110). I am
> > doubtful if that's the solution to your problem however, as you say that
> > the scanner starts out working correctly...
> >
> > Also, the output of scanimage -L is correct? The access rights? There is
> > a group called scanner, which I put the users in as well.
> >
> > Andreas
> >
>
> Thanks for the reply. No, it doesn't work for me. The first time I run
> xsane everything seems to go as expected except that no picture appears.
> Then I have to repower the scanner to get it recognized again. It
> therefore seems as if the problem is in processing the output from the
> scanner, rather than in getting it to run.
>
> Both scanimage -L and sane-find-scanner show the scanner is there, and
> so does cat /proc/bus/usb/devices.
>
> Google shows some people with similar problems (different scanners) but
> no obvious solutions. I'm beginning to wonder if it is a hardware
> problem of some sort, for the following reasons:
>
> 1. It developed in a system which was working previously.
> 2. I reverted to the previous version of xsane, but no help.
> 3. I tried 3 different kernels: no help.
>
> But my laptop (almost identical setup) does work with the scanner, so it
> seems unlikely that it has developed a fault. I'm completely floored by
> this.
I too, have been ticked off by this one. It is affecting my ability to
do business. I even tried my HP ScanJet 6390C usb-scanner, I still have.
It to is screwed. I borrowed a friends UMAX 3400 usb-scanner too, yep
borked!
I was working for 15 days with my new Epson RX600. Printing still works
JUST FINE, but scanning *IS HOSED*.
I reverted... to the revision I had when I installed the scanner. No
joy. Something else is bad. I also purged (all printing and scanning
software) restarted the machine from COLD (printer/scanner) and
computer. The re-installed, no joy.
Maybe we should look at the packages, seems libusb was compiled on Feb
2, 2005. That is the right amount of time for it to get through
incoming...etc
Yep, Libusb-0.1-4 v1:0.1.9-2 is the culprit. Revert to the version in
Sarge, by going to http://packages.debian.org/testing/libs/libusb-0.1-4
And downloading for your architecture.
---------------------------------------
Received: (at 294667-done) by bugs.debian.org; 11 Feb 2005 00:34:45 +0000
>From [EMAIL PROTECTED] Thu Feb 10 16:34:43 2005
Return-path: <[EMAIL PROTECTED]>
Received: from farad.aurel32.net [82.232.2.251]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CzOle-00038z-00; Thu, 10 Feb 2005 16:34:42 -0800
Received: from bode.aurel32.net ([2001:618:400:6439:2e0:18ff:fea3:b80f])
by farad.aurel32.net with esmtp (TLS-1.0:RSA_ARCFOUR_SHA:16)
(Exim 4.34)
id 1CzOld-0001eH-G6; Fri, 11 Feb 2005 01:34:41 +0100
Received: from aurel32 by bode.aurel32.net with local (Exim 4.34)
id 1CzOld-0005wA-1N; Fri, 11 Feb 2005 01:34:41 +0100
Date: Fri, 11 Feb 2005 01:34:41 +0100
From: Aurelien Jarno <[EMAIL PROTECTED]>
To: Greg Folkert <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Subject: Re: Bug#294667: libusb-0.1-4: Libusb-0.1-4 v1:0.1.9-2 Will not read
data properly from USB Scanners, corrupts output.
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
X-Mailer: Mutt 1.5.6+20040907i (CVS)
User-Agent: Mutt/1.5.6+20040907i
Sender: Aurelien Jarno <[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=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
On Thu, Feb 10, 2005 at 07:10:40PM -0500, Greg Folkert wrote:
> Package: libusb-0.1-4
> Version: 1:0.1.9-2
> Severity: grave
> Justification: renders package unusable
>
> This package renders nearly any device access with libusb impossible. Things
> are being griped about on D-D and D-U.
The bug is fixed in version 1:0.1.9-3 which is now in Sid an should be
available on the mirrors. Please upgrade to the latest version.
Closing the bug.
--
.''`. Aurelien Jarno GPG: 1024D/F1BCDB73
: :' : Debian GNU/Linux developer | Electrical Engineer
`. `' [EMAIL PROTECTED] | [EMAIL PROTECTED]
`- people.debian.org/~aurel32 | www.aurel32.net
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
