Bug#300317: sane-utils: scanimage -L does not return
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 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]
Bug#300317: sane-utils: scanimage -L does not return
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 silverboxy kernel: ppdev0: unregistered pardevice Mar 25 22:30:48 silverboxy kernel: parport0: ppdev0 forgot to release port Mar 25 22:30:48 silverboxy kernel: ppdev0: unregistered pardevice Mar 25 22:30:56 silverboxy kernel: ppdev0: registered pardevice Mar 25 22:30:57 silverboxy kernel: ppdev0: released pardevice because user-space forgot Mar 25 22:30:57 silverboxy kernel: ppdev0: unregistered pardevice Does that tell you anything? I am looking at this problem, but I'd need an strace from the mustek backend -- I don't understand why this one hangs. Could you do that just as you did for the hpsj5s backend ? 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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#300317: sane-utils: scanimage -L does not return
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 unfinished ... silverboxy:~# OK, exact same thing. I'm going to ask you for one (really, two) debug logs from the mustek and hpsj5s backends, and I should have enough information to pinpoint the problem. (btw, I guess you still see the same parport related messages in /var/log/messages ?). Could you run: # SANE_DEBUG_MUSTEK=255 scanimage -L 2 mustek.log # SANE_DEBUG_HPSJ5S=255 scanimage -L 2 hpsj5s.log And send me both files ? (I still think both backends are misusing libieee1284 and not releasing the parport; otherwise, the parport is claimed by another process, and there's nothing I can do I think) Thanks, 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]
Bug#300317: sane-utils: scanimage -L does not return
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: unregistered pardevice Mar 30 23:20:25 silverboxy kernel: parport0: ppdev0 forgot to release port Mar 30 23:20:25 silverboxy kernel: ppdev0: unregistered pardevice Mar 30 23:20:28 silverboxy kernel: ppdev0: registered pardevice Mar 30 23:20:29 silverboxy kernel: ppdev0: registered pardevice Mar 30 23:21:38 silverboxy kernel: ppdev0: released pardevice because user-space forgot Mar 30 23:21:38 silverboxy kernel: ppdev0: unregistered pardevice Mar 30 23:21:38 silverboxy kernel: parport0: ppdev0 forgot to release port Mar 30 23:21:38 silverboxy kernel: ppdev0: unregistered pardevice Mar 30 23:22:06 silverboxy kernel: ppdev0: registered pardevice Mar 30 23:22:06 silverboxy kernel: ppdev0: registered pardevice Mar 30 23:22:56 silverboxy kernel: ppdev0: released pardevice because user-space forgot Mar 30 23:22:56 silverboxy kernel: ppdev0: unregistered pardevice Mar 30 23:22:56 silverboxy kernel: parport0: ppdev0 forgot to release port Mar 30 23:22:56 silverboxy kernel: ppdev0: unregistered pardevice I attach logs from mustek and hpsj5s (which is very short). Thanks, Rainer Am Mittwoch, 30. März 2005 23:02 schrieb 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 unfinished ... silverboxy:~# OK, exact same thing. I'm going to ask you for one (really, two) debug logs from the mustek and hpsj5s backends, and I should have enough information to pinpoint the problem. (btw, I guess you still see the same parport related messages in /var/log/messages ?). Could you run: # SANE_DEBUG_MUSTEK=255 scanimage -L 2 mustek.log # SANE_DEBUG_HPSJ5S=255 scanimage -L 2 hpsj5s.log And send me both files ? (I still think both backends are misusing libieee1284 and not releasing the parport; otherwise, the parport is claimed by another process, and there's nothing I can do I think) Thanks, JB. -- Rainer Dorsch Alzentalstr. 28 D-71083 Herrenberg 07032-919495 Icq: 32550367 [sanei_debug] Setting debug level of mustek to 255. [mustek] SANE mustek backend version 1.0 build 137 from sane-backends 1.0.15 [mustek] sane_init: authorize != null [mustek] sane_init: using sanei_scsi_open_extended [mustek] sane_init: reading config file `mustek.conf' [mustek] sane_init: config file line 1: ignoring comment line [mustek] sane_init: config file line 2: ignoring empty line [mustek] sane_init: config file line 3: ignoring comment line [mustek] sane_init: config file line 4: ignoring comment line [mustek] sane_init: config file line 5: ignoring comment line [mustek] sane_init: config file line 6: ignoring comment line [mustek] sane_init: config file line 7: ignoring comment line [mustek] sane_init: config file line 8: ignoring comment line [mustek] sane_init: config file line 9: ignoring empty line [mustek] sane_init: config file line 10: ignoring comment line [mustek] sane_init: config file line 11: trying to attach `scsi MUSTEK * Scanner' [mustek] sane_init: config file line 12: ignoring comment line [mustek] sane_init: config file line 13: ignoring comment line [mustek] sane_init: config file line 14: ignoring comment line [mustek] sane_init: config file line 15: ignoring comment line [mustek] sane_init: config file line 16: ignoring comment line [mustek] sane_init: config file line 17: ignoring empty line [mustek] sane_init: config file line 18: trying to attach `scsi SCANNER' [mustek] sane_init: config file line 19: ignoring comment line [mustek] sane_init: config file line 20: ignoring comment line [mustek] sane_init: config file line 21: ignoring comment line [mustek] sane_init: config file line 22: ignoring comment line [mustek] sane_init: config file line 23: ignoring comment line [mustek] sane_init: config file line 24: ignoring empty line [mustek] sane_init: config file line 25: trying to attach `/dev/scanner' [mustek] attach: trying device /dev/scanner [mustek] dev_open /dev/scanner [mustek] dev_open: Invalid argument: can't open /dev/scanner as a SCSI device [mustek] dev_open: Invalid argument: can't open /dev/scanner as an AB306N device [sanei_debug] Setting debug level of hpsj5s to 255. [hpsj5s] sane_init[hpsj5s] sane_init: version_code != 0, authorize != 0 [hpsj5s] sane_init: SANE hpsj5s backend version 1.0.3 [hpsj5s] sane_init
Bug#300317: sane-utils: scanimage -L does not return
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 pardevice because user-space forgot Mar 25 22:30:48 silverboxy kernel: ppdev0: unregistered pardevice Mar 25 22:30:48 silverboxy kernel: parport0: ppdev0 forgot to release port Mar 25 22:30:48 silverboxy kernel: ppdev0: unregistered pardevice Mar 25 22:30:56 silverboxy kernel: ppdev0: registered pardevice Mar 25 22:30:57 silverboxy kernel: ppdev0: released pardevice because user-space forgot Mar 25 22:30:57 silverboxy kernel: ppdev0: unregistered pardevice Does that tell you anything? I need to investigate a bit, but it tells me where to start. Thanks! 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]
Bug#300317: sane-utils: scanimage -L does not return
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 (/etc/init.d/cupsys stop) does not solve the problem. If you have the lp module loaded, it might it that claimed the parport (I'd have to look at the code to be sure, it's been a long time). silverboxy:~# lsmod |grep lp lp 11204 0 parport41832 3 lp,parport_pc,ppdev silverboxy:~# that, apart from disabling the backends by default :/ I would do this only when we understood why libieee1284 is now a problem or when more people are complaining. As it hasn't been reported so far, I believe there is something specific to your setup... Could you have a look to /var/log/messages and see if you can find any message related to the parallel port in there ? silverboxy:~# grep parport /var/log/messages silverboxy:~# grep parport /var/log/syslog Mar 25 10:17:57 silverboxy kernel: parport0: BUSY timeout (1) in compat_write_block_pio Mar 25 22:30:48 silverboxy kernel: parport0: ppdev0 forgot to release port silverboxy:~# grep 1284 /var/log/syslog silverboxy:~# grep 1284 /var/log/messages silverboxy:~# 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 pardevice because user-space forgot Mar 25 22:30:48 silverboxy kernel: ppdev0: unregistered pardevice Mar 25 22:30:48 silverboxy kernel: parport0: ppdev0 forgot to release port Mar 25 22:30:48 silverboxy kernel: ppdev0: unregistered pardevice Mar 25 22:30:56 silverboxy kernel: ppdev0: registered pardevice Mar 25 22:30:57 silverboxy kernel: ppdev0: released pardevice because user-space forgot Mar 25 22:30:57 silverboxy kernel: ppdev0: unregistered pardevice Does that tell you anything? Thanks, Rainer libieee1284 claims the parallel port so that the kernel will load the driver if it isn't loaded already; maybe it could be patched to check that the driver is loaded to avoid this situation... which driver? it=hpsj5s could be patched? libieee1284 itself. If you agree, I'll close this bug. Yes, please do so. We understood the problem is specific for my system and the solution is documented in BTS. I'll wait a little bit more, I'd really like to understand what's going on, and I have the feeling that it's something terribly simple that just hasn't popped up to my mind yet ... Many thanks for the great support. You're welcome :-) JB. -- Rainer Dorsch Alzentalstr. 28 D-71083 Herrenberg 07032-919495 Icq: 32550367
Bug#300317: sane-utils: scanimage -L does not return
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 scanimage stopping at hpsj5s. Commenting out hpsj5s as well makes scanimage returning OK, somehow both backends didn't like what you had on your parallel port, it seems. ...but it is still not fully working: silverboxy:~# scanimage -L device `umax1220u:libusb:001:005' is a UMAX Astra 1220U flatbed scanner silverboxy:~# scanimage --lamp-off --device-name=umax1220u:libusb:001:005 scanimage: sane_start: Invalid argument silverboxy:~# 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)? 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. If it works that way, then the scanner is getting confused by another backend checking for one of its supported devices. I am just wondering, was there recently a sane upgrade in sarge (or why do I see now all these issues???). Not in the last 3 weeks. 1.0.15-8 will hit Sarge in a couple of days. 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]
Bug#300317: sane-utils: scanimage -L does not return
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]
Bug#300317: sane-utils: scanimage -L does not return
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]
Bug#300317: sane-utils: scanimage -L does not return
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 parallel port before. Try without cups running if you want to be sure. There's no good way to avoid that, apart from disabling the backends by default :/ libieee1284 claims the parallel port so that the kernel will load the driver if it isn't loaded already; maybe it could be patched to check that the driver is loaded to avoid this situation... If you agree, I'll close this bug. 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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#300317: sane-utils: scanimage -L does not return
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 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 (/etc/init.d/cupsys stop) does not solve the problem. that, apart from disabling the backends by default :/ I would do this only when we understood why libieee1284 is now a problem or when more people are complaining. libieee1284 claims the parallel port so that the kernel will load the driver if it isn't loaded already; maybe it could be patched to check that the driver is loaded to avoid this situation... which driver? it=hpsj5s could be patched? If you agree, I'll close this bug. Yes, please do so. We understood the problem is specific for my system and the solution is documented in BTS. Many thanks for the great support. Rainer -- Rainer Dorsch Alzentalstr. 28 D-71083 Herrenberg 07032-919495 Icq: 32550367
Bug#300317: sane-utils: scanimage -L does not return
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 support for Astra 2200 [umax] (C) 1997-2002 by Oliver Rauch [umax] EMAIL: [EMAIL PROTECTED] [umax] reading configure file umax.conf [umax] sanei_config_attach_matching_devices(scsi UMAX * Scanner) [umax] sanei_config_attach_matching_devices(scsi LinoHell JADE) [umax] sanei_config_attach_matching_devices(scsi LinoHell Office) [umax] sanei_config_attach_matching_devices(scsi LinoHell Office2) [umax] sanei_config_attach_matching_devices(scsi LinoHell SAPHIR2) [umax] sanei_config_attach_matching_devices(scsi LinoHell SAPHIR3) [umax] sanei_config_attach_matching_devices(scsi Linotype SAPHIR4) [umax] sanei_config_attach_matching_devices(scsi LinoHell OPAL2) [umax] sanei_config_attach_matching_devices(scsi HDM LS4H1S) [umax] sanei_config_attach_matching_devices(scsi Nikon AX-110) [umax] sanei_config_attach_matching_devices(scsi Nikon AX-210) [umax] sanei_config_attach_matching_devices(scsi KYE ColorPage-HR5) [umax] sanei_config_attach_matching_devices(scsi EPSON Perfection600) [umax] sanei_config_attach_matching_devices(scsi ESCORT Galleria 600S) [umax] sanei_config_attach_matching_devices(scsi TriGem PowerScanII) [umax] sanei_usb_attach_matching_devices(usb 0x1606 0x0230) [umax] option connection-type = 1 [umax] attach_scanner: /dev/scanner, connection_type 1 [umax] attach_scanner: opening scsi device /dev/scanner [umax] ERROR: attach_scanner: opening scsi device /dev/scanner failed [umax] option connection-type = 2 [umax] attach_scanner: /dev/usbscanner, connection_type 2 [umax] attach_scanner: opening usb device /dev/usbscanner [umax] sanei_umaxusb_open: open of `/dev/usbscanner' failed: Invalid argument [umax] ERROR: attach_scanner: opening usb device /dev/usbscanner failed [umax] finished reading configure file [umax] sane_get_devices(local_only = 0) When I run as user, the problem does not occur: [EMAIL PROTECTED]:~$ scanimage -L device `umax1220u:libusb:001:004' is a UMAX Astra 1220U flatbed scanner [EMAIL PROTECTED]:~$ 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 support for Astra 2200 [umax] (C) 1997-2002 by Oliver Rauch [umax] EMAIL: [EMAIL PROTECTED] [umax] reading configure file umax.conf [umax] sanei_config_attach_matching_devices(scsi UMAX * Scanner) [umax] sanei_config_attach_matching_devices(scsi LinoHell JADE) [umax] sanei_config_attach_matching_devices(scsi LinoHell Office) [umax] sanei_config_attach_matching_devices(scsi LinoHell Office2) [umax] sanei_config_attach_matching_devices(scsi LinoHell SAPHIR2) [umax] sanei_config_attach_matching_devices(scsi LinoHell SAPHIR3) [umax] sanei_config_attach_matching_devices(scsi Linotype SAPHIR4) [umax] sanei_config_attach_matching_devices(scsi LinoHell OPAL2) [umax] sanei_config_attach_matching_devices(scsi HDM LS4H1S) [umax] sanei_config_attach_matching_devices(scsi Nikon AX-110) [umax] sanei_config_attach_matching_devices(scsi Nikon AX-210) [umax] sanei_config_attach_matching_devices(scsi KYE ColorPage-HR5) [umax] sanei_config_attach_matching_devices(scsi EPSON Perfection600) [umax] sanei_config_attach_matching_devices(scsi ESCORT Galleria 600S) [umax] sanei_config_attach_matching_devices(scsi TriGem PowerScanII) [umax] sanei_usb_attach_matching_devices(usb 0x1606 0x0230) [umax] option connection-type = 1 [umax] attach_scanner: /dev/scanner, connection_type 1 [umax] attach_scanner: opening scsi device /dev/scanner [umax] ERROR: attach_scanner: opening scsi device /dev/scanner failed [umax] option connection-type = 2 [umax] attach_scanner: /dev/usbscanner, connection_type 2 [umax] attach_scanner: opening usb device /dev/usbscanner [umax] sanei_umaxusb_open: open of `/dev/usbscanner' failed: Invalid argument [umax] ERROR: attach_scanner: opening usb device /dev/usbscanner failed [umax] finished reading configure file [umax] sane_get_devices(local_only = 0) device `umax1220u:libusb:001:004' is a UMAX Astra 1220U flatbed scanner [umax] sane_exit [EMAIL PROTECTED]:~$ OK... probably not a problem in the backend. Could you run scanimage under gdb and obtain a backtrace ? 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]
Bug#300317: sane-utils: scanimage -L does not return
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 `umax1220u:libusb:001:004' is a UMAX Astra 1220U flatbed scanner [umax] sane_exit [EMAIL PROTECTED]:~$ OK... probably not a problem in the backend. 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 Bye, Henning -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#300317: sane-utils: scanimage -L does not return
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 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]
Bug#300317: sane-utils: scanimage -L does not return
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] This is sane-umax version 1.0 build 44 [umax] compiled with USB support for Astra 2200 [umax] (C) 1997-2002 by Oliver Rauch [umax] EMAIL: [EMAIL PROTECTED] [umax] reading configure file umax.conf [umax] sanei_config_attach_matching_devices(scsi UMAX * Scanner) [umax] sanei_config_attach_matching_devices(scsi LinoHell JADE) [umax] sanei_config_attach_matching_devices(scsi LinoHell Office) [umax] sanei_config_attach_matching_devices(scsi LinoHell Office2) [umax] sanei_config_attach_matching_devices(scsi LinoHell SAPHIR2) [umax] sanei_config_attach_matching_devices(scsi LinoHell SAPHIR3) [umax] sanei_config_attach_matching_devices(scsi Linotype SAPHIR4) [umax] sanei_config_attach_matching_devices(scsi LinoHell OPAL2) [umax] sanei_config_attach_matching_devices(scsi HDM LS4H1S) [umax] sanei_config_attach_matching_devices(scsi Nikon AX-110) [umax] sanei_config_attach_matching_devices(scsi Nikon AX-210) [umax] sanei_config_attach_matching_devices(scsi KYE ColorPage-HR5) [umax] sanei_config_attach_matching_devices(scsi EPSON Perfection600) [umax] sanei_config_attach_matching_devices(scsi ESCORT Galleria 600S) [umax] sanei_config_attach_matching_devices(scsi TriGem PowerScanII) [umax] sanei_usb_attach_matching_devices(usb 0x1606 0x0230) [umax] option connection-type = 1 [umax] attach_scanner: /dev/scanner, connection_type 1 [umax] attach_scanner: opening scsi device /dev/scanner [umax] ERROR: attach_scanner: opening scsi device /dev/scanner failed [umax] option connection-type = 2 [umax] attach_scanner: /dev/usbscanner, connection_type 2 [umax] attach_scanner: opening usb device /dev/usbscanner [umax] sanei_umaxusb_open: open of `/dev/usbscanner' failed: Invalid argument [umax] ERROR: attach_scanner: opening usb device /dev/usbscanner failed [umax] finished reading configure file [umax] sane_get_devices(local_only = 0) When I run as user, the problem does not occur: [EMAIL PROTECTED]:~$ scanimage -L device `umax1220u:libusb:001:004' is a UMAX Astra 1220U flatbed scanner [EMAIL PROTECTED]:~$ 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 support for Astra 2200 [umax] (C) 1997-2002 by Oliver Rauch [umax] EMAIL: [EMAIL PROTECTED] [umax] reading configure file umax.conf [umax] sanei_config_attach_matching_devices(scsi UMAX * Scanner) [umax] sanei_config_attach_matching_devices(scsi LinoHell JADE) [umax] sanei_config_attach_matching_devices(scsi LinoHell Office) [umax] sanei_config_attach_matching_devices(scsi LinoHell Office2) [umax] sanei_config_attach_matching_devices(scsi LinoHell SAPHIR2) [umax] sanei_config_attach_matching_devices(scsi LinoHell SAPHIR3) [umax] sanei_config_attach_matching_devices(scsi Linotype SAPHIR4) [umax] sanei_config_attach_matching_devices(scsi LinoHell OPAL2) [umax] sanei_config_attach_matching_devices(scsi HDM LS4H1S) [umax] sanei_config_attach_matching_devices(scsi Nikon AX-110) [umax] sanei_config_attach_matching_devices(scsi Nikon AX-210) [umax] sanei_config_attach_matching_devices(scsi KYE ColorPage-HR5) [umax] sanei_config_attach_matching_devices(scsi EPSON Perfection600) [umax] sanei_config_attach_matching_devices(scsi ESCORT Galleria 600S) [umax] sanei_config_attach_matching_devices(scsi TriGem PowerScanII) [umax] sanei_usb_attach_matching_devices(usb 0x1606 0x0230) [umax] option connection-type = 1 [umax] attach_scanner: /dev/scanner, connection_type 1 [umax] attach_scanner: opening scsi device /dev/scanner [umax] ERROR: attach_scanner: opening scsi device /dev/scanner failed [umax] option connection-type = 2 [umax] attach_scanner: /dev/usbscanner, connection_type 2 [umax] attach_scanner: opening usb device /dev/usbscanner [umax] sanei_umaxusb_open: open of `/dev/usbscanner' failed: Invalid argument [umax] ERROR: attach_scanner: opening usb device /dev/usbscanner failed [umax] finished reading configure file [umax] sane_get_devices(local_only = 0) device `umax1220u:libusb:001:004' is a UMAX Astra 1220U flatbed scanner [umax] sane_exit [EMAIL PROTECTED]:~$ OK... probably not a problem in the backend. Could you run scanimage under gdb and obtain a backtrace ? In your other mail you asked for another trace (?): silverboxy:~# SANE_DEBUG_DLL=255 SANE_DEBUG_UMAX1220U=255 scanimage -L [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_init/read_config: reading dll.conf [dll] add_backend: adding backend `net' [dll] add_backend: adding
Bug#300317: sane-utils: scanimage -L does not return
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 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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#300317: sane-utils: scanimage -L does not return
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 documentation which came with this software (README, FAQ, manpages). [EMAIL PROTECTED]:~$ su - Password: silverboxy:~# scanimage -L Note: scanimage does not return to the command line. silverboxy:~# lsusb Bus 004 Device 001: ID : Bus 003 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 003 Device 001: ID : Bus 002 Device 001: ID : Bus 001 Device 004: ID 1606:0010 Umax [hex] Astra 1220U Bus 001 Device 001: ID : silverboxy:~# The scanner is visible at usb level, KDE's kooka can use it flawlessly. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (600, 'testing'), (300, 'unstable'), (200, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.7-1-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages sane-utils depends on: ii adduser 3.63 Add and remove users and g:roups ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an ii libieee1284-3 0.2.8-2 Cross-platform library for paralle ii libjpeg62 6b-9 The Independent JPEG Group's JPEG ii libsane 1.0.15-7 API library for scanners ii libusb-0.1-42:0.1.10a-6 userspace USB programming library -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
