Rainer Dorsch <[EMAIL PROTECTED]> wrote: >> Does scanning as a user work ? Could you try to unplug the scanner, >> plug it in again, and try to scan (without running scanimage -L first)? > > Yes, it does.
Good. >> If that works, try moving umax1220u at the top of the list in >> /etc/sane.d/dll.conf, and try running scanimage -L then scanimage. > > Works as well. Expected. >> If it works that way, then the scanner is getting confused by another >> backend checking for one of its supported devices. > > [EMAIL PROTECTED]:~$ scanimage -L > device `umax1220u:libusb:001:007' is a UMAX Astra 1220U flatbed scanner > [EMAIL PROTECTED]:~$ /usr/bin/scanimage --lamp-off > --device=umax1220u:libusb:001:007 > scanimage: sane_start: Invalid argument > [EMAIL PROTECTED]:~$ /usr/bin/scanimage > --device-name=umax1220u:libusb:001:007 > --format=pnm --resolution=300 -l 9.3 -t 1 -x 210 -y 297 > 123.pnm > [EMAIL PROTECTED]:~$ > > Seems that the --lamp-off device specific option has some specific problems. Yes. Could you send a log of scanimage --lamp-off ? > But although there is an error message, it seems that the option is working > at least the scanner lamp goes off. The log should help in understanding what's going on. > That makes we wondering, what is going on. I call scanimage -L in a > bootup-script. I.e. the system hang during boot-up, starting when I opened > the bugreport, i.e. a many days after the last sane upgrade. Did you change anything to your configuration in the meantime ? What is attached to your parallel port ? > My conclusions right now: > > - The --lamp-off option is working the error message might be there for a > long > time I'll try to get a status on that once I'll have the log. > - The mustek and hpsj5s drivers block the scanimage -L in sarge since a few > days. Reason is unknown. They were probably blocking on the parallel port, for some reason. > What is the right way from here on that ensures that: > > - I do not have the problem back with the next upgrade (dpkg will probably > warn that a config file was modified, dll.conf) The conffile won't change without you noticing, so you're safe. > - Others are not running in the same problem Ideally, only the backend you need should be enabled in dll.conf; unfortunately, people want SANE working out of the box, so... Moreover, your problem is probably related to what is attached to your parallel port; if it was a common problem, we would know about it. 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]
