Bug#300317: sane-utils: scanimage -L does not return

2005-03-31 Thread Julien BLACHE
Rainer Dorsch [EMAIL PROTECTED] wrote: Hi Rainer, I attach logs from mustek and hpsj5s (which is very short). Thanks, I'll try to find out what's going on. It may take some time. JB. -- Julien BLACHE - Debian GNU/Linux Developer - [EMAIL PROTECTED] Public key available on

Bug#300317: sane-utils: scanimage -L does not return

2005-03-30 Thread Julien BLACHE
Rainer Dorsch [EMAIL PROTECTED] wrote: Hi Rainer, Mar 25 22:30:45 silverboxy kernel: ppdev0: registered pardevice Mar 25 22:30:46 silverboxy kernel: ppdev0: registered pardevice Mar 25 22:30:48 silverboxy kernel: ppdev0: released pardevice because user-space forgot Mar 25 22:30:48

Bug#300317: sane-utils: scanimage -L does not return

2005-03-30 Thread Julien BLACHE
Rainer Dorsch [EMAIL PROTECTED] wrote: Hi Rainer, open(/dev/scanner, O_RDWR|O_NONBLOCK|O_EXCL) = -1 ENOENT (No such file or directory) open(/etc/ieee1284.conf, O_RDONLY)= -1 ENOENT (No such file or directory) open(/dev/parport0, O_RDONLY|O_NOCTTY) = 5 ioctl(5, PPCLAIM, 0x4004c7bc

Bug#300317: sane-utils: scanimage -L does not return

2005-03-30 Thread Rainer Dorsch
Hi Julien, the syslog contains Mar 30 23:20:22 silverboxy kernel: ppdev0: registered pardevice Mar 30 23:20:24 silverboxy kernel: ppdev0: registered pardevice Mar 30 23:20:25 silverboxy kernel: ppdev0: released pardevice because user-space forgot Mar 30 23:20:25 silverboxy kernel: ppdev0:

Bug#300317: sane-utils: scanimage -L does not return

2005-03-26 Thread Julien BLACHE
Rainer Dorsch [EMAIL PROTECTED] wrote: Hi Rainer, The second line in syslog is caused by the scanimage -L (?): Mar 25 22:30:45 silverboxy kernel: ppdev0: registered pardevice Mar 25 22:30:46 silverboxy kernel: ppdev0: registered pardevice Mar 25 22:30:48 silverboxy kernel: ppdev0: released

Bug#300317: sane-utils: scanimage -L does not return

2005-03-25 Thread Rainer Dorsch
Julien, sorry for the late reply. Am Sonntag, 20. März 2005 23:21 schrieben Sie: Rainer Dorsch [EMAIL PROTECTED] wrote: I guess cups might have claimed the parallel port before. Try without cups running if you want to be sure. There's no good way to avoid Stopping cups

Bug#300317: sane-utils: scanimage -L does not return

2005-03-20 Thread Julien BLACHE
Rainer Dorsch [EMAIL PROTECTED] wrote: [dll] init: initializing backend `mustek' Does it stop at this point ? If yes, try to comment the mustek backend in /etc/sane.d/dll.conf. Might be the mustek backend hanging on the parallel port or something. Commenting out mustek and makes it

Bug#300317: sane-utils: scanimage -L does not return

2005-03-20 Thread Julien BLACHE
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

Bug#300317: sane-utils: scanimage -L does not return

2005-03-20 Thread Julien BLACHE
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

Bug#300317: sane-utils: scanimage -L does not return

2005-03-20 Thread Julien BLACHE
Rainer Dorsch [EMAIL PROTECTED] wrote: open(/etc/ieee1284.conf, O_RDONLY)= -1 ENOENT (No such file or directory) open(/dev/parport0, O_RDONLY|O_NOCTTY) = 4 ioctl(4, PPCLAIM, 0x4009ccce unfinished ... silverboxy:~# I guess cups might have claimed the

Bug#300317: sane-utils: scanimage -L does not return

2005-03-20 Thread Rainer Dorsch
Am Sonntag, 20. März 2005 20:21 schrieben Sie: Rainer Dorsch [EMAIL PROTECTED] wrote: open(/etc/ieee1284.conf, O_RDONLY)= -1 ENOENT (No such file or directory) open(/dev/parport0, O_RDONLY|O_NOCTTY) = 4 ioctl(4, PPCLAIM, 0x4009ccce unfinished ... silverboxy:~# I guess cups might

Bug#300317: sane-utils: scanimage -L does not return

2005-03-19 Thread Julien BLACHE
Rainer Dorsch [EMAIL PROTECTED] wrote: [please keep the bug log in the loop when replying] It is umax: silverboxy:~# SANE_DEBUG_UMAX=255 scanimage -L [sanei_debug] Setting debug level of umax to 255. [umax] sane_init [umax] This is sane-umax version 1.0 build 44 [umax] compiled with USB

Bug#300317: sane-utils: scanimage -L does not return

2005-03-19 Thread Henning Meier-Geinitz
Hi, On Sat, Mar 19, 2005 at 12:17:27PM +0100, Julien BLACHE wrote: [root]: [umax] finished reading configure file [umax] sane_get_devices(local_only = 0) (freeze) ... [user]: [umax] finished reading configure file [umax] sane_get_devices(local_only = 0) device

Bug#300317: sane-utils: scanimage -L does not return

2005-03-19 Thread Julien BLACHE
Henning Meier-Geinitz [EMAIL PROTECTED] wrote: Not in the umax backend but maybe in the umax1220u or some other backend. Try SANE_DEBUG_DLL=255 SANE_DEBUG_UMAX1220U=255 scanimage -L Right, missed it; looks like I badly need some sleep. That's the thing to do. JB. -- Julien BLACHE [EMAIL

Bug#300317: sane-utils: scanimage -L does not return

2005-03-19 Thread Rainer Dorsch
Am Samstag, 19. März 2005 12:17 schrieb Julien BLACHE: Rainer Dorsch [EMAIL PROTECTED] wrote: [please keep the bug log in the loop when replying] It is umax: silverboxy:~# SANE_DEBUG_UMAX=255 scanimage -L [sanei_debug] Setting debug level of umax to 255. [umax] sane_init [umax]

Bug#300317: sane-utils: scanimage -L does not return

2005-03-19 Thread Julien BLACHE
Rainer Dorsch [EMAIL PROTECTED] wrote: silverboxy:~# scanimage -L Note: scanimage does not return to the command line. Debug log, please. SANE_DEBUG_UMAX=255 scanimage -L If your backend isn't the umax backend, replace UMAX by the backend name. JB. -- Julien BLACHE - Debian GNU/Linux

Bug#300317: sane-utils: scanimage -L does not return

2005-03-18 Thread Rainer Dorsch
Package: sane-utils Version: 1.0.15-7 Severity: normal [EMAIL PROTECTED]:~$ scanimage -L No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the