Diab Jerius <[EMAIL PROTECTED]> wrote: Hi Diab,
> Ok, I purged libsane-extras and ran the following experiment. I ran > scanimage -L 10 times in a row (log files are L.n.log) and then ran > scanimage in acquire mode 10 times (logs are in read.n.log). The script > test-sane is what does it. > > There are separate directories for 1.0.15-9 and 1.0.15-8. A tar file > of the logs is here: > > http://hea-www.cfa.harvard.edu/~dj/tmp/sane/20050508.1.tar.bz2 Thanks. I relocated the file to <http://people.debian.org/~jblache/308081/> > Note that the -L runs alternate between "normal" behavior and > lots of resource errors. OK. Does your scanner use a firmware ? > In both 1.0.15-8 and 1.0.15-9, the second attempt at acquiring an > image (read.1.log) succeeds. > > (For 1.0.15-8 I cycled power to the scanner and tried just acquiring > the image. The behavior was the same as when it was preceded with the > scanimage -L runs.) > > with libsane at 1.0.15-9, I then downgraded libusb and ran the script. > > 0.1.10a-8: same behavior > > 0.1.10a-7: at this point I modified test-sane to use 5 iterations (10 > was taking too long), with the result that the image was > acquired on the first attempt. Otherwise, the pattern of > success/failure. > > 0.1.10a-6: same > 0.1.10a-5: same > 0.1.10a-3: same > > Finally, I downgraded to > > libsane: 1.0.15-1 > libusb-0.1-4: 0.1.10a-3 > > Just to be sure, I rebooted after this. Same results. > > I wish I could tell you when I last had the scanner working, so as to > narrow things down. > > Any further downgrades on libusb causes a small dependency crisis; > I'll need a bit more time to prepare for that and won't be able to do > anything until Tuesday evening. Ok. Looks like a real problem. JB. -- Julien BLACHE <[EMAIL PROTECTED]> | Debian, because code matters more Debian & GNU/Linux Developer | <http://www.debian.org> 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]
