https://bugzilla.novell.com/show_bug.cgi?id=408518 Bernhard Novell König changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P1 - Urgent -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=408518 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=408518#c2 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsmeix@novell.com, jsrain@novell.com AssignedTo|jsmeix@novell.com |bnc-team-screening@forge.provo.novell.com Component|Update Problems |Kernel QAContact|jsrain@novell.com |kernel-maintainers@forge.provo.novell.com Summary|scanimage on HP5370C terminates with signal, |after kernel update scanimage does no longer |nothing scanned |work --- Comment #2 from Johannes Meixner 2008-07-17 05:18:54 MDT --- Because in comment #0 you wrote that "This error occures since the zypper has installed the last kernel-update, bevor this the program was working correctly." it is most likely not a bug in the scanning software but a bug in the kernel. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=408518 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=408518#c3 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gqs@pabxas.com.au --- Comment #3 from Johannes Meixner 2008-07-17 05:32:02 MDT --- *** Bug 406112 has been marked as a duplicate of this bug. *** https://bugzilla.novell.com/show_bug.cgi?id=406112 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=408518 User bk90de@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=408518#c5 Bernhard Novell König changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bk90de@gmx.de Status|NEEDINFO |NEW Info Provider|bk90de@gmx.de | --- Comment #5 from Bernhard Novell König 2008-08-25 13:53:19 MDT --- ok after installing sane-backends-debuginfo: (I can't find any other libsane-debuginfo and sane-backends-debuginfo has a file called /usr/lib/debug/usr/bin/scanimage.debug) I the syntax of any command has to be different, please tell me. //First try: bhl@linux-b4ca:~> gdb scanimage --symbols=/usr/lib/debug/usr/bin/scanimage.debug GNU gdb 6.6.50.20070726-cvs Copyright (C) 2007 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "x86_64-suse-linux"... Using host libthread_db library "/lib64/libthread_db.so.1". (gdb) r Starting program: /usr/bin/scanimage [Thread debugging using libthread_db enabled] [New Thread 0x2af2f49ecb00 (LWP 31531)] scanimage: no SANE devices found Program exited with code 01. (gdb) r -d avision:libusb:002:002 --resolution 300dpi Starting program: /usr/bin/scanimage -d avision:libusb:002:002 --resolution 300dpi [Thread debugging using libthread_db enabled] [New Thread 0x2b4bf10e6b00 (LWP 31549)] Program received signal SIGTERM, Terminated. [Switching to Thread 0x2b4bf10e6b00 (LWP 31549)] 0x00002b4bf0dd1e47 in kill () from /lib64/libc.so.6 (gdb) bt #0 0x00002b4bf0dd1e47 in kill () from /lib64/libc.so.6 #1 0x00002b4bf10ee983 in do_cancel () from /usr/lib64/sane/libsane-avision.so.1 #2 0x00002b4bf10f414f in sane_avision_start () from /usr/lib64/sane/libsane-avision.so.1 #3 0x00000000004042cc in main () #4 0x00002b4bf0dbeb54 in __libc_start_main () from /lib64/libc.so.6 #5 0x0000000000401a09 in _start () (gdb) /// resetting the scanner, other try in the same session of gdb: (gdb) r -d avision:libusb:002:003 The program being debugged has been started already. Start it from the beginning? (y or n) y Starting program: /usr/bin/scanimage -d avision:libusb:002:003 [Thread debugging using libthread_db enabled] [New Thread 0x2b0c8ff12b00 (LWP 31838)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x2b0c8ff12b00 (LWP 31838)] 0x00002b0c8ff1de25 in sort_and_average () from /usr/lib64/sane/libsane-avision.so.1 (gdb) bt #0 0x00002b0c8ff1de25 in sort_and_average () from /usr/lib64/sane/libsane-avision.so.1 #1 0x00002b0c8ff1e1a3 in normal_calibration () from /usr/lib64/sane/libsane-avision.so.1 #2 0x00002b0c8ff1f953 in sane_avision_start () from /usr/lib64/sane/libsane-avision.so.1 #3 0x00000000004042cc in main () #4 0x00002b0c8fbeab54 in __libc_start_main () from /lib64/libc.so.6 #5 0x0000000000401a09 in _start () /// I hope this can help, but for me its not looks so, therefore what must I do with the debug-info? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=408518 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=408518#c7 --- Comment #7 from Johannes Meixner 2008-09-05 00:43:22 MDT --- Only for your information (I am really neither a kernel nor a libusb expert): I think the interesting error message in the strace is "scanimage: open of device avision:libusb:003:004 failed: Invalid argument". But I have no idea what the "Invalid argument" actually is. I assume that an libusb call fails but I have no idea which call fails and why it fails. Perhaps "dmesg" shows something regarding USB at that time? Perhaps you get more meaningful messages when you do the "Trouble-Shooting (Debugging)" as described at http://en.opensuse.org/SDB:Configuring_Scanners_from_SUSE_LINUX_9.2 i.e. do something like (see man sane-usb): ----------------------------------------------------------------- export SANE_DEBUG_DLL=4 export SANE_DEBUG_AVISION=7 export SANE_DEBUG_SANEI_USB=128 scanimage -d avision:libusb:xxx:yyy -T && echo OK || echo FAILED ----------------------------------------------------------------- Some background information: Usually when a scanner driver for SCSI and USB scanners starts, it scans the SCSI bus and the USB to find matching scanners. Because you have a USB scanner, there are the SCSI failures. To avoid the useless SCSI scan in your case, it should help to specify only you exact model in your driver's config file, see "man sane-avision", e.g. have in /etc/sane.d/avision.conf an active line like usb 0x03f0 0x0701 Preferably do the above described "Trouble-Shooting (Debugging)" with such a line in /etc/sane.d/avision.conf to avoid tons of meaningless messages when the whole SCSI bus and USB is scanned only to find your scanner. By the way: What is in your /etc/sane.d/avision.conf? My default one has no active line (which usually means the driver does autoprobing of the SCSI bus and USB). But I don't have a scanner to test this driver myself. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=408518 User bk90de@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=408518#c9 Bernhard Novell König changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|bk90de@gmx.de | --- Comment #9 from Bernhard Novell König 2008-09-05 13:53:22 MDT --- Created an attachment (id=237975) --> (https://bugzilla.novell.com/attachment.cgi?id=237975) debugprotocol of scan, terminating at sort_and_average() a) my "/etc/sane.d/avision.conf" had only commented lines for this test I uncomment the line: usb 03f0 0701 b) This test was done with the default-version which was installed at my computer. It breaks at the same position like the debug-version of the scanimage. c) The Debug resultes from the following commands: SCANPARAM="-d avision:`sane-find-scanner|grep libusb|sed 's#^.*libusb#libusb#'`" export SANE_DEBUG_DLL=4 export SANE_DEBUG_AVISION=7 export SANE_DEBUG_SANEI_USB=128 ( scanimage ${SCANPARAM} -T && echo OK || echo FAILED ) > $TMP/x 2>&1 the last line in the debug-file was produced from the shell-echo. Exists any chance to understand the sort_and_average() - Problem? I don't see any error, but the Program terminates with only some initial and small moves of the scanner lamp, after this the scanner lamp flashing (= Error). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=408518 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=408518#c11 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |bk90de@gmx.de --- Comment #11 from Johannes Meixner 2008-10-09 00:28:27 MDT --- And I don't see any real error or failure in attachment #237975. The communication seems to work well, see the "wanted xx bytes, got xx bytes" lines. On the other hand why has it worked before the kernel update but fails after the kernel update without being a kernel issue? Regarding the stop at sort_and_average(): Some backends (drivers) do not implement the cancel correctly, see bug #344534 but then "scanimage -d... >/dev/null" should work which does not work here according to comment #0. But here is seems to be different because there is no "cancel" in attachment #237975. Usually one should find something like "sane_cancel" in the debugging output but here it seems it just hangs while doing sort_and_average for the color calibration. attachment #237975 reads ----------------------------------------------------------------------- [avision] sane_init: parsing config line "#option disable-calibration" [avision] sane_init: config file line 9: ignoring comment line . . . [avision] normal_calibration: . . . [avision] normal_calibration: using color calibration .. [avision] get_calib_data: Got 167076 bytes calibration data [avision] sort_and_average: ----------------------------------------------------------------------- Perhaps you just have to wait a longer time until the sort_and_average has finished? Try if it works when you activate in /etc/sane.d/avision.conf the line "option disable-calibration" so that no calibration is done, see "man sane-avision": ------------------------------------------------------------- disable-calibration: Disables the scanner's color calibration. You might try this if your scans hang or only produces random garbage. ------------------------------------------------------------- Then retry the test with "scanimage -d... -T" and if this does not work try also "scanimage -d... >/dev/null" If it works now it is really no bug in the kernel but was just a random coincidence. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=408518 User bk90de@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=408518#c13 Bernhard Novell König changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|bk90de@gmx.de | --- Comment #13 from Bernhard Novell König 2008-10-09 14:36:15 MDT --- OK something happend, but so success. 1) with an uncommented line option disable-calibration in /etc/sane.d/avision.conf I found some changes: the commands SCANPARAM=" -d avision:`sane-find-scanner|grep libusb|sed 's#^.*libusb#libusb#'`" scanimage ${SCANPARAM} -T produces some line of output: scanimage: scanning image of size 1272x1741 pixels at 24 bits/pixel scanimage: acquiring RGB frame, 8 bits/sample scanimage: reading one scanline, 3816 bytes... PASS scanimage: reading one byte... PASS scanimage: stepped read, 2 bytes... PASS scanimage: stepped read, 4 bytes... PASS scanimage: stepped read, 8 bytes... PASS scanimage: stepped read, 16 bytes... PASS scanimage: stepped read, 32 bytes... PASS scanimage: stepped read, 64 bytes... PASS scanimage: stepped read, 128 bytes... PASS scanimage: stepped read, 256 bytes... PASS scanimage: stepped read, 512 bytes... PASS scanimage: stepped read, 1024 bytes... PASS scanimage: stepped read, 2048 bytes... PASS scanimage: stepped read, 4096 bytes... PASS scanimage: stepped read, 4095 bytes... PASS scanimage: stepped read, 2047 bytes... PASS scanimage: stepped read, 1023 bytes... PASS scanimage: stepped read, 511 bytes... PASS scanimage: stepped read, 255 bytes... PASS scanimage: stepped read, 127 bytes... PASS scanimage: stepped read, 63 bytes... PASS scanimage: stepped read, 31 bytes... PASS scanimage: stepped read, 15 bytes... PASS scanimage: stepped read, 7 bytes... PASS scanimage: stepped read, 3 bytes... PASS but after this the scanner leaves the lamp in the final position, not at the startposition. I can repeat this command and the scanner goes to the start and repeats the result. 2) if i call with a rebooted scanner the command scanimage ${SCANPARAM} --resolution 300dpi > file (that'is my standard command) it produces a file with some scanned picture, but this picture has all colours in vertical lines over the picture, that means I can see, that the picture was scanned but grafically it is not acceptable for a scan. 3) the following scan without the resolution-parameter produces a rare noise at the end of the scan and scanimage ${SCANPARAM} > file scanimage: sane_read: Error during device I/O on a rebooted scanner scanimage -v ${SCANPARAM} > file scanimage: scanning image of size 1272x1741 pixels at 24 bits/pixel scanimage: acquiring RGB frame .. here comes a long pause after the scanner goes with noise to his startposition scanimage: min/max graylevel value = 0/255 scanimage: sane_read: Error during device I/O 4) switching on the debug-environment like in the older comment and running scanimage ${SCANPARAM} --resolution 300dpi -v > file 2>2 the last lines showing [sanei_usb] 32490:FF 43 19 FF 49 15 FF 4C 0B FF 51 0B FF 53 08 FF C..I..L..Q..S.. [sanei_usb] 324A0:57 09 34 5B 0F 32 67 0D 3C 65 0A 38 64 0B 24 6C W.4[.2g. (interrupt read) going down ... [sanei_usb] sanei_usb_read_int: trying to read 1 bytes [sanei_usb] sanei_usb_read_int: wanted 1 bytes, got 1 bytes [sanei_usb] 0000: 00 ............... [avision] <== (interrupt read) got: 1, status: 0 [avision] reader_process: stripe filled: 297648 [avision] reader_process: useful_bytes 206064 [dll] sane_read(handle=0x61a1f0,data=0x61dc30,maxlen=32768,lenp=0x7fff9df4ec6c) [dll] sane_read(handle=0x61a1f0,data=0x61dc30,maxlen=32768,lenp=0x7fff9df4ec6c) [dll] sane_read(handle=0x61a1f0,data=0x61dc30,maxlen=32768,lenp=0x7fff9df4ec6c) [dll] sane_read(handle=0x61a1f0,data=0x61dc30,maxlen=32768,lenp=0x7fff9df4ec6c) [dll] sane_read(handle=0x61a1f0,data=0x61dc30,maxlen=32768,lenp=0x7fff9df4ec6c) [avision] reader_process: end of iteration [avision] reader_process: i/o loop finished [avision] release unit: type: 0 [avision] filling command to have a length of 10, was: 6 [avision] Timeouts: write: 30000, read: 30000, status: 10000 [sanei_usb] sanei_usb_write_bulk: trying to write 10 bytes [sanei_usb] 0000: 17 00 00 00 00 00 00 00 00 00 ............... [dll] sane_read(handle=0x61a1f0,data=0x61dc30,maxlen=32768,lenp=0x7fff9df4ec6c) [dll] sane_read(handle=0x61a1f0,data=0x61dc30,maxlen=32768,lenp=0x7fff9df4ec6c) [sanei_usb] sanei_usb_write_bulk: wanted 10 bytes, wrote 10 bytes [avision] avision_usb_status: timeout 10000, 1 retries [avision] ==> (interrupt read) going down ... [sanei_usb] sanei_usb_read_int: trying to read 1 bytes [sanei_usb] sanei_usb_read_int: wanted 1 bytes, got 1 bytes [sanei_usb] 0000: 00 ............... [avision] <== (interrupt read) got: 1, status: 0 [avision] reader_process: returning success [dll] sane_read(handle=0x61a1f0,data=0x61dc30,maxlen=32768,lenp=0x7fff9df4ec6c) [avision] sane_read: got 0 bytes, err: 11 Resource temporarily unavailable [avision] do_eof: [avision] do_eof: returning 5 scanimage: min/max graylevel value = 0/255 scanimage: read 26582256 bytes in total [dll] sane_cancel(handle=0x61a1f0) [avision] sane_cancel: [avision] do_cancel: [dll] sane_close(handle=0x61a1f0) [avision] sane_close: [sanei_usb] sanei_usb_close: closing device 0 [dll] sane_exit: exiting [dll] sane_exit: calling backend `avision's exit function [avision] sane_exit: [dll] sane_exit: finished // ther is a line saying [avision] sane_read: got 0 bytes, err: 11 Resource temporarily unavailable with strace I don't found a signal-11 exception but the strace-protocol is very large... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=408518 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=408518#c15 --- Comment #15 from Johannes Meixner 2008-10-10 00:08:53 MDT --- By the way: Have a look at bug 419565 which is for openSUSE 11.0 but perhaps after your kernel update there is a similar issue on your system? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.