Rainer Dorsch <[EMAIL PROTECTED]> wrote: >> > Seems that the --lamp-off device specific option has some specific >> > problems. >> >> Yes. Could you send a log of scanimage --lamp-off ? > > silverboxy:~# SANE_DEBUG_DLL=255 SANE_DEBUG_UMAX1220U=255 scanimage > --lamp-off > --device-name=umax1220u:libusb:001:004 > [sanei_debug] Setting debug level of dll to 255. > [dll] sane_init: SANE dll backend version 1.0.11 from sane-backends 1.0.15 [...] > [dll] sane_start(handle=0x80539a8) > [umax1220u] sane_start > [umax1220u] UMAX_set_scan_parameters: > [umax1220u] color = 1 > [umax1220u] xo = 0, yo = 0 > [umax1220u] w = 0, h = 0 > [umax1220u] xres = 75, yres = 75 > [umax1220u] left = 0, top = 0 > [umax1220u] right = 0, bottom = 0 > scanimage: sane_start: Invalid argument
OK. The backend's default window size is 0x0 pixels (as written in the manpage); setting a scan area will make the warning go away. >> Did you change anything to your configuration in the meantime ? What >> is attached to your parallel port ? > > I did the usual apt-get upgrade and I installed xdebconfigurator (hwinfo, > kudzu, and dependecies), but I deinstalled again. Shouldn't matter. > On the parallel port, I have a Canon BJ-10sx printer, but that is there since > a long time. Can a new version of cups have such a side effect? No. You could strace scanimage with the 2 blocking backends, maybe that would help understand what's going on. (if you do so, *please* enable only *one* of the backends, otherwise the strace log will be *HUGE* and unreadable :/) >> The conffile won't change without you noticing, so you're safe. > > Correct, but then I have the choice between manual updating the new version > of > the conf file or not getting all the new stuff in the new version. dll.conf won't change much in the upcoming months/years; few backends get added to SANE these days, and apart from removing the hpoj and hpaio backend from dll.conf, there's no other change planned. >> 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. > > If it is related to the BJ-10 then I agree, that model is not out there very > often any more ;-) With the parallel port, you never really know what's going on ... > ...but, when I switch off the printer, the problem is still there, even if I > unplug the cable from the printer. That would mean everybody with "nothing" > on the parallel port should have the problem. There's something else, then. 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]
