libsane_1.0.19~cvs20071028-1_amd64.deb works fine indeed.
Thanks for the tip about /var/log/dpkg.log: 8 years with Debian, still I didn't know this... It confirms the date where the problem appeared 2007-12-27 00:34:31 upgrade libsane 1.0.19~cvs20070730-1 1.0.19~cvs20071213-1 Thanks, Looking forward to hearing from your next release, Vincent > "Vincent LAFAGE" <[EMAIL PROTECTED]> wrote: > > Hi, > >> with libsane version 1.0.19~cvs20070505-3ubuntu2 >> the scanner is working correctly. (I just tried it). > > Great, thanks. > >> I remember scanning was OK on December 5th. >> Then I did not try it again before the end of December (about 26th), >> then it started failing. > >> I am updating my "testing" configuration on an almost daily basis: an >> arguable choice, still it may help you pinpoint when the problematic >> version reached testing repository, and soon after, my computer. > > Thanks, that nails down the problem to the change I suspected in the > CVS. That's very good, thanks. > >> I don't know how to display a package update history, if such an >> information is kept. > > There's /var/log/dpkg.log for the next time you'll need that :) > > > In the meantime I suggest you downgrade to a version earlier than > 1.0.19~cvs20071213-1 (1.0.19~cvs20071028-1 should be fine, if not > please report back) as I don't plan to fix that in the current > snapshot and there's a release planned in 4 weeks. > > 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
