http://bugzilla.opensuse.org/show_bug.cgi?id=1005673 http://bugzilla.opensuse.org/show_bug.cgi?id=1005673#c2 Dominique Leuenberger changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(suse.junky@t-onli | |ne.de) | --- Comment #2 from Dominique Leuenberger --- (In reply to Dominique Leuenberger from comment #1)

That's not the default version from 42.1 - so the main question for now would be if we REALLY see a regression between 42.1 and 42.2 or if you fixed this in 42.1 already by adding this package.

Can you attempt to build this version for 42.2 as well and test if it would solve your issue?

Ups - I just see you have a Canon Scanner - so hplip should not ever make a difference there -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1005673 Dominique Leuenberger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsmeix@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1005673 http://bugzilla.opensuse.org/show_bug.cgi?id=1005673#c5 Bit Juggler changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High --- Comment #5 from Bit Juggler --- (In reply to Johannes Meixner from comment #4)

USB scanner I/O errors are usually related to lower level USB stuff i.e. libusb or kernel.

Currently there are issues with USB3 i.e. when the xhci kernel module is used for the USB bus where the scanner is connected to, check 'lsusb -t'

Cf. https://bugzilla.opensuse.org/show_bug.cgi?id=955079#c2

lsusb -t /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M |__ Port 3: Dev 2, If 0, Class=Vendor Specific Class, Driver=btusb, 12M |__ Port 3: Dev 2, If 1, Class=Vendor Specific Class, Driver=btusb, 12M |__ Port 3: Dev 2, If 2, Class=Vendor Specific Class, Driver=btusb, 12M |__ Port 3: Dev 2, If 3, Class=Application Specific Interface, Driver=, 12M => |__ Port 4: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 480M |__ Port 9: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 9: Dev 4, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 9: Dev 4, If 2, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 10: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 10: Dev 5, If 1, Class=Human Interface Device, Driver=usbhid, 12M

# lsusb -v -s 1:3 Bus 001 Device 003: ID 04a9:1907 Canon, Inc. CanoScan LiDE 700F Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 255 Vendor Specific Subclass bDeviceProtocol 255 Vendor Specific Protocol bMaxPacketSize0 64 idVendor 0x04a9 Canon, Inc. idProduct 0x1907 CanoScan LiDE 700F bcdDevice 6.03 iManufacturer 1 Canon iProduct 2 CanoScan iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 39 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 255 Vendor Specific Subclass bInterfaceProtocol 255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0001 1x 1 bytes bInterval 8 Device Qualifier (for other device speed): bLength 10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 255 Vendor Specific Subclass bDeviceProtocol 255 Vendor Specific Protocol bMaxPacketSize0 64 bNumConfigurations 1 Device Status: 0x0000 (Bus Powered) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1005673 http://bugzilla.opensuse.org/show_bug.cgi?id=1005673#c7 --- Comment #7 from Bit Juggler --- Just connected the scanner to my friends Laptop which has openSUSE 42.1 and openSUSE 42.2 RC1 installed as well but is a much older device (no USB3.0 at all). Same behavior: Scanner works with openSUSE 42.1 but fails in openSUSE 42.2 RC1.

lsusb Bus 008 Device 004: ID 04f2:b033 Chicony Electronics Co., Ltd Bus 008 Device 002: ID 04a9:1907 Canon, Inc. CanoScan LiDE 700F Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 002: ID 24ae:2001 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 003: ID 08ff:1600 AuthenTec, Inc. AES1600 Bus 003 Device 002: ID 0b05:1751 ASUSTek Computer, Inc. BT-253 Bluetooth Adapter Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

lsusb -t /: Bus 08.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=, 480M |__ Port 5: Dev 4, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 5: Dev 4, If 1, Class=Video, Driver=uvcvideo, 480M /: Bus 07.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M /: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 1: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 1: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M |__ Port 1: Dev 2, If 2, Class=Vendor Specific Class, Driver=, 12M |__ Port 1: Dev 2, If 3, Class=Application Specific Interface, Driver=, 12M |__ Port 2: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M

Here no "xhci_hcd" is used but "ehci-pci". Looking at the logfile produced by scanimage --clear-calibration --preview --mode Color 1>calibrate.pnm 2>calibrate.log one can see that many interactions with the scanner work (on both machines!) until [genesys] genesys_flatbed_calibration: led calibration failed: Error during device I/O [genesys] genesys_start_scan: failed to do scanner calibration: Error during device I/O so it is hard to belief that the problem is related to USB. Nevertheless i will try sane-backends 1.0.25 from http://download.opensuse.org/repositories/graphics/openSUSE_Leap_42.2/ to see whether that cures the problem. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1005673 http://bugzilla.opensuse.org/show_bug.cgi?id=1005673#c9 --- Comment #9 from ray herman --- (In reply to Bit Juggler from comment #7)

so it is hard to belief that the problem is related to USB.

I agree. I have also tried (without success) a forced “libKF5Sane5-16.08.2-1.1” from Tumbleweed. But to do that properly (resolving all dependencies) would mean changing Mesa, KDE PIM, Akonadi and a lot of QT5 libraries, which would not leave much resembling Leap-42.2-RC1. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1005673 http://bugzilla.opensuse.org/show_bug.cgi?id=1005673#c11 --- Comment #11 from ray herman --- (In reply to ray herman from comment #10)

P.P.S. The use in Tumbleweed of libKF5Sane5-16.08.1-1.1.x86_64 from 42.2-RC1 gives prevents scanning. ____________________________________ rayh@y3:~> rpm -qa libKF5Sane5 libKF5Sane5-16.08.1-1.1.x86_64 rayh@y3:~> 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). rayh@y3:~> lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 048d:8386 Integrated Technology Express, Inc. Bus 001 Device 003: ID 1bcf:2c43 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 0489:e07a Foxconn / Hon Hai Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub rayh@y3:~> lsusb -t /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/11p, 480M |__ Port 4: Dev 2, If 0, Class=Vendor Specific Class, Driver=btusb, 12M |__ Port 4: Dev 2, If 1, Class=Vendor Specific Class, Driver=btusb, 12M |__ Port 4: Dev 2, If 2, Class=Vendor Specific Class, Driver=btusb, 12M |__ Port 4: Dev 2, If 3, Class=Application Specific Interface, Driver=, 12M |__ Port 7: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 7: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M |__ Port 8: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 12M rayh@y3:~> ___________________________________________ And reverting to libKf5Sane from Tumbleweed while retaining 42.2-RC1 sane-backends: ____________________________________________ rayh@y3:~> rpm -qa libKF5Sane5 libKF5Sane5-16.08.2-1.1.x86_64 rayh@y3:~> scanimage -L device `genesys:libusb:001:008' is a Canon LiDE 110 flatbed scanner rayh@y3:~> lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 048d:8386 Integrated Technology Express, Inc. Bus 001 Device 003: ID 1bcf:2c43 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 0489:e07a Foxconn / Hon Hai Bus 001 Device 008: ID 04a9:1909 Canon, Inc. CanoScan LiDE 110 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub rayh@y3:~> lsusb -t /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/11p, 480M |__ Port 1: Dev 8, If 0, Class=Vendor Specific Class, Driver=, 480M |__ Port 4: Dev 2, If 0, Class=Vendor Specific Class, Driver=btusb, 12M |__ Port 4: Dev 2, If 1, Class=Vendor Specific Class, Driver=btusb, 12M |__ Port 4: Dev 2, If 2, Class=Vendor Specific Class, Driver=btusb, 12M |__ Port 4: Dev 2, If 3, Class=Application Specific Interface, Driver=, 12M |__ Port 7: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 7: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M |__ Port 8: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 12M rayh@y3:~> _________________________________________ -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1005673 http://bugzilla.opensuse.org/show_bug.cgi?id=1005673#c13 Dominique Leuenberger changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo? --- Comment #13 from Dominique Leuenberger --- (In reply to ray herman from comment #11)

(In reply to ray herman from comment #10)

...

P.P.S. The use in Tumbleweed of libKF5Sane5-16.08.1-1.1.x86_64 from 42.2-RC1 gives prevents scanning.

Very interesting find! (to some degree surprising, as scanimage does not make use of this lib) Tumbleweed by now should have caught up with KDE Applications 16.08.2 - if this library is indeed the culprit, the issue should now also be visible on an up-to-date Tumbleweed system (starting with snapshot 20161018) Can you confirm this? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1005673 http://bugzilla.opensuse.org/show_bug.cgi?id=1005673#c14 --- Comment #14 from Bit Juggler --- After i went back to sane-backends Version 1.0.24-4.39 on my openSUSE 42.2 RC1 i did this very rude test: I copied the files /usr/lib64/libusb-0.1.so.4.4.4 (22,3 KiB; libusb-0_1-4 Version 0.1.13-31.1) /usr/lib64/libusb-1.0.so.0.1.0 (95,0 KiB; libusb-1_0-0 Version 1.0.20-1.1) from my openSUSE 42.1 installation to my openSUSE 42.2 RC1 installation to replace there the files /usr/lib64/libusb-0.1.so.4.4.4 (22,4 KiB; libusb-0_1-4 Version 0.1.13-32.4) /usr/lib64/libusb-1.0.so.0.1.0 (95,1 KiB; libusb-1_0-0 Version 1.0.20-3.4) and the scanner worked (but probably there will be problems with other USB-devices, i have not tested yet). So i have to to wear sackcloth and ashes: USB seems to be at least part of the problem. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1005673 http://bugzilla.opensuse.org/show_bug.cgi?id=1005673#c16 --- Comment #16 from Johannes Meixner --- I am not at all a USB expert but from my point of view comment#14 indicates the root cause is in libusb (or in whatever lower level stuff that is used by it). Bit Juggler, don't worry - you do not need wear sackcloth and ashes. Acutally I am very thankful for your various tests and for your detailed hard facts in this bug report which is a valuable contribution to openSUSE. Many thanks for it! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1005673 http://bugzilla.opensuse.org/show_bug.cgi?id=1005673#c18 --- Comment #18 from Bit Juggler --- (In reply to Johannes Meixner from comment #16)

I am not at all a USB expert but from my point of view comment#14 indicates the root cause is in libusb (or in whatever lower level stuff that is used by it).

How can i investigate that in more detail? Do i have to report that problem somewhere else (I don't want to put it on the SANE maillinglist if it is an USB problem)? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1005673 http://bugzilla.opensuse.org/show_bug.cgi?id=1005673#c21 --- Comment #21 from Bit Juggler --- Created attachment 698941 --> http://bugzilla.opensuse.org/attachment.cgi?id=698941&action=edit Logfile from scanimage -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1005673 http://bugzilla.opensuse.org/show_bug.cgi?id=1005673#c23 --- Comment #23 from Bit Juggler --- (In reply to Stanislav Brabec from comment #19)

Is there anything interesting in the syslog?

journalctl -x -e

I ran the following test (as "root" immediately after system start):

...

...

... >>>

# setup environment for debugging export SANE_DEBUG_GENESYS=255 export SANE_DEBUG_GENESYS_LOW=255 export SANE_DEBUG_GENESYS_GL124=255 export SANE_DEBUG_GENESYS_GL646=255 export SANE_DEBUG_GENESYS_GL841=255 export SANE_DEBUG_GENESYS_GL843=255 export SANE_DEBUG_GENESYS_GL847=255 export SANE_DEBUG_SANEI_USB=128 # get system log before scanning journalctl -x -e >journalctl_output_before_scan.txt # calibrate scanner and do a preview scanimage --clear-calibration --preview --mode Color 1>calibrate.pnm 2>calibrate.log # get system log after scanning journalctl -x -e >journalctl_output_after_scan.txt <<< ... <<< The file calibrate.pnm is empty. No other .pnm files were produced. Find the following files attached: journalctl_output_before_scan.txt calibrate.log journalctl_output_after_scan.txt -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1005673 http://bugzilla.opensuse.org/show_bug.cgi?id=1005673#c25 Bit Juggler changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 - Medium |P2 - High Severity|Normal |Major --- Comment #25 from Bit Juggler --- A bug that renders a once flawless working piece of hardware completely useless is of "medium severity" ??? I guess i don't wont to know what the consequences of a "major" or even "critical" bug are - will it cause my system to explode? A "paperless" office makes a working scanner an essential device. Without a working scanner me (and some of my customers) will not be able to migrate to openSUSE 42.2. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1005673 http://bugzilla.opensuse.org/show_bug.cgi?id=1005673#c27 --- Comment #27 from Bit Juggler ---

From https://bugzilla.opensuse.org/page.cgi?id=importance_matrix.html :

Normal: Regular issue, some loss of functionality under specific circumstances So if a piece of hardware that worked flawless with openSUSE 42.1, 13.2 and probably some versions before gets rendered useless (not just on some occasions but all the time) then you call that "... some loss of functionality under specific circumstances"? Well, as Morpheus said: "Welcome to the desert of the real!" -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1005673 http://bugzilla.opensuse.org/show_bug.cgi?id=1005673#c29 Stanislav Brabec changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kernel-maintainers@forge.pr | |ovo.novell.com Flags| |needinfo?(kernel-maintainer | |s@forge.provo.novell.com) --- Comment #29 from Stanislav Brabec --- Comment 21: The scanning syslog contains only one line. But it is very interesting: Okt 24 15:28:17 TESTBED kernel: usb 3-4: reset high-speed USB device number 3 using xhci_hcd It indicates posible kernel problem. (timeout change? I remember similar issues, where certain scanners did not work with certain USB/SCSI drivers. The really faulty was the scanner firmware that was too slow. But most drivers were tolerant to it.) The scanning log shows following problem: [genesys_low] sanei_genesys_read_gl847_register(0x41)=0xfd [genesys_low] status=PWRBIT BUFEMPTY FEEDFSH SCANFSH HOMESNR LAMPSTS MOTORENB [sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 4, value = 142, index = 16418, len = 2 [sanei_usb] 000 B3 55 .U [genesys_low] sanei_genesys_read_gl847_register(0x40)=0xb3 [genesys_gl847] gl847_stop_action completed [genesys_gl847] gl847_led_calibration: Error during device I/O [genesys] genesys_flatbed_calibration: led calibration failed: Error during device I/O [genesys] genesys_start_scan: failed to do scanner calibration: Error during device I/O [genesys] sane_genesys_start: Error during device I/O scanimage: sane_start: Error during device I/O [genesys] sane_genesys_cancel start So it seems that LED callibration command causes USB communication to die. Comment 14: It looks very strange. Both libusb-1_0 and libusb-compat have exactly the same source in Leap 42.1 and Leap 42.2. There are just two builds from identical sources. Is it reproducible (i. e. break, install files from 42.1, succeed, replace by 42.2 files and break again)? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1005673 http://bugzilla.opensuse.org/show_bug.cgi?id=1005673#c31 --- Comment #31 from Stanislav Brabec --- Thanks. Now it makes more sense. - libusb was probably false positive. - The real problem is caused by the scanner firmware or by kernel, but it is probably triggered by the new SANE driver. Is there any difference between USB 2 and USB 3? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1005673 http://bugzilla.opensuse.org/show_bug.cgi?id=1005673#c32 Oliver Neukum changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(kernel-maintainer | |s@forge.provo.novell.com) | --- Comment #32 from Oliver Neukum --- (In reply to Stanislav Brabec from comment #31)

Thanks. Now it makes more sense.

- libusb was probably false positive.

- The real problem is caused by the scanner firmware or by kernel, but it is probably triggered by the new SANE driver.

It looks like that. The kernel will not reset a scanner on its own initiative. If this is a firmware issue, the best (and possibly only) option is bisecting SANE and finding the command that trips up the scanner's firmware. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1005673 http://bugzilla.opensuse.org/show_bug.cgi?id=1005673#c34 --- Comment #34 from Bit Juggler --- Created attachment 699539 --> http://bugzilla.opensuse.org/attachment.cgi?id=699539&action=edit Content of journal before scan (USB3.0) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1005673 http://bugzilla.opensuse.org/show_bug.cgi?id=1005673#c36 --- Comment #36 from Bit Juggler --- Created attachment 699543 --> http://bugzilla.opensuse.org/attachment.cgi?id=699543&action=edit Content of journal after scan (USB3.0) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1005673 http://bugzilla.opensuse.org/show_bug.cgi?id=1005673#c38 --- Comment #38 from Bit Juggler --- (In reply to Takashi Iwai from comment #37)

You can install openSUSE-42.1 kernel onto your 42.2 system and boot it.

My openSUSE 42.1 installation runs with kernel 4.8.4-1.g402d8c1-default from http://download.opensuse.org/repositories/Kernel:/stable/standard/. I tried that kernel with openSUSE 42.2 RC1 already (comment #24). The scanner did not work. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1005673 http://bugzilla.opensuse.org/show_bug.cgi?id=1005673#c40 --- Comment #40 from Johannes Meixner --- Only a side note FYI from a total USB innocent: USB3 (xhci) issues exist since a longer time in the kernel. This does of course not mean that there couldn't also be general USB issues in SANE (usual SANE scanner drivers us the general USB functionality in SANE) or particular issues in a particular scanner driver (e.g. genesys). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1005673 http://bugzilla.opensuse.org/show_bug.cgi?id=1005673#c42 --- Comment #42 from Oliver Neukum --- (In reply to Luca Beltrame from comment #41)

Perhaps a naive question: what would happen if USB autosuspend is disabled for this scanner? I have a scanner that does not play with SANE too well unless I disable autosuspend for it.

Opening a device through libusb resumes the device and prevents further suspends. If autosuspend is to blame, it should fail right away and not at a specific place. If you have a specific scanner that needs autosuspend disabled, please open a separate bug report and assign it to me. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1005673 http://bugzilla.opensuse.org/show_bug.cgi?id=1005673#c44 --- Comment #44 from Stanislav Brabec --- Comment 43: Could you confirm these findings: Leap 42.1 works out of the box. Leap 42.2 does not scan out of the box. Leap 42.2 with downgrade of sane from 42.1 works. Leap 42.2 with downgrade of kernel from 42.1 does not scan. => This all indicates that bug trigger is inside sane. But first line breaks that idea: Leap 42.1 works, even if you upgrade both kernel and sane from 42.2. Is it real and reproducible? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1005673 http://bugzilla.opensuse.org/show_bug.cgi?id=1005673#c46 --- Comment #46 from ray herman --- (In reply to Stanislav Brabec from comment #44)

Comment 43:

Could you confirm these findings:

Leap 42.1 works out of the box.

I have just performed an update of a stock Leap-42.1 that has a similar scanner attached. Sane does not recognise the scanner. :~> uname -rv 4.1.34-33-default #1 SMP PREEMPT Thu Oct 20 08:03:29 UTC 2016 (fe18aba) :~> rpm -qa libusb-* libusb-1_0-0-1.0.20-1.1.x86_64 libusb-0_1-4-0.1.13-31.1.x86_64 :~> rpm -qa sane-backends* sane-backends-autoconfig-1.0.24-3.7.x86_64 sane-backends-1.0.24-3.7.x86_64 :~> lsusb Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 002: ID 0924:3d59 Xerox Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 003: ID 0461:4d20 Primax Electronics, Ltd HP Optical Mouse Bus 006 Device 002: ID 03f0:0024 Hewlett-Packard KU-0316 Keyboard Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04a9:2220 Canon, Inc. CanoScan LIDE 25 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub :~> scanimage -L No scanners were identified. If you ... Trying to detect the scanner with YaST (ncurses) gives: “Not Configured:Canon CanoScan USB scanner (vendor=0x04a9 [Canon], product=0x2220 [CanoScan]) at libusb:001:002” and an attempt to use a Plustek driver. This looks like a regression to [Bug 672059] in openSuSE-11.4!

Leap 42.2 does not scan out of the box.

That was my experience before the lamp on my Canoscan Lide 110 failed.

Leap 42.1 works, even if you upgrade both kernel and sane from 42.2.

Is it real and reproducible?

I will try this out later on the remote 42.1 with a Canoscan Lide 25. I had tried the libsane-genesys.so.1.0.23 from openSUSE-13.1 without success. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1005673 http://bugzilla.opensuse.org/show_bug.cgi?id=1005673#c48 Bit Juggler changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(suse.junky@t-onli | |ne.de) | --- Comment #48 from Bit Juggler --- (In reply to Stanislav Brabec from comment #47)

Thanks. So let's stop testing different combinations, and return to a clean 42.2.

Yesterday i already did a new, clean (formatted /- and /home-partition) installation of openSUSE 42.2 RC1. Actually i planned to upgrade this to openSUSE RC2 as soon as that is available (tomorrow?). So i guess i should stay with 42.2 RC1? Please advice me how to proceed best.

It seems that the trigger (but probably not the bug itself) could be caught by bisecting of sane.

I never bisected a library up to now but with you giving advice i should be able to do that.

If you have an old kernel works with a clean 42.2 (with new sane), we can try to bisect kernel.

Sorry, i do have NO kernel for openSUSE 42.2 RC1 that works with version of sane supplied by openSUSE 42.2 RC1 (1.0.24-4.39). I'm not sure whether i understand this correctly: Bisecting the kernel? Why when the problem is in libsane (or even in libsane-genesys)? Which version do you address by "new sane"? The version from the openSUSE 42.2 RC1 OSS repository (1.0.24-4.39) or the version from OBS (1.0.25-116.5)? If sane AND kernel shall be bisected then we are back to several combinations (and i understood you actually wanted to avoid this)?

Do you have enough knowledges to run bisect on your machine? (Basically it means checkout of sane or kernel using git, then compilation of the code (in an optimal case), testing it with scanimage, answering to git bisect. Then git gives you another snapshot of the code and the process repeats until git identifies exact change that breaks it.

If you can do it, I can provide a detailed manual.

As i said: With some support i might be able to handle this.

If you can't we have to generate a library snapshot, wait for your test report, generate a new library snapshot etc.

So this sounds like testing only sane. That's what i would prefer anyway because we already know that sane 1.0.24-4.39 from openSUSE 42.2 RC1 does not work with the openSUSE 42.2 RC1 kernel (4.4.25-4.1) nor with one of the latest kernels from http://download.opensuse.org/repositories/Kernel:/stable/standard/ (4.8.4-1.g402d8c1-default). Please give me further advice on how to proceed best in order to support you. Thank you. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1005673 http://bugzilla.opensuse.org/show_bug.cgi?id=1005673#c50 --- Comment #50 from Bit Juggler --- (In reply to Stanislav Brabec from comment #49)

One of bug ideas was: SANE is only a trigger, real bug is in the kernel. Let's stop to talk about this (at least for now).

Even if SANE is only a bug trigger, the breaking commit could help a lot. And if SANE itself causes the bug, it will be caught as well.

If the tests shall be done with openSUSE 42.2 RC1 then we will need a openSUSE 42.2 RC1 kernel to start the bisect with. There have been only two kernels so far for openSUSE 42.2 RC1 (4.4.24-1.1, 4.4.25-4.1) and none of them did make sane working with my scanner. So what kernel and what sane version shall we start with? Shall we exchange all the information around the testing (i.e. if i need your advice) via bugzilla or shall we communicate via mail directly with each other? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1005673 http://bugzilla.opensuse.org/show_bug.cgi?id=1005673#c52 --- Comment #52 from ray herman --- This machine is now running Leap-42.2-RC2 with one major variation -- kernel-4.7.6 and Broadcom wireless drivers from Tumbleweed and Packman. Attached is a Canoscan LiDE 110 wit non-working lamp. sysman@toyb:~> lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 048d:8386 Integrated Technology Express, Inc. Bus 001 Device 003: ID 5986:0535 Acer, Inc Bus 001 Device 002: ID 0489:e07a Foxconn / Hon Hai Bus 001 Device 005: ID 04a9:1909 Canon, Inc. CanoScan LiDE 110 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub sysman@toyb:~> scanimage -L device `genesys:libusb:001:005' is a Canon LiDE 110 flatbed scanner sysman@toyb:~> scanimage -T scanimage: scanning image of size 636x885 pixels at 8 bits/pixel scanimage: acquiring gray frame, 8 bits/sample scanimage: reading one scanline, 636 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, 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 sysman@toyb:~> ____________________ When I changed the symbolic link for /usr/lib64/libusb-1.0.so.0 to reference /usr/lib64/libusb-1.0.so.0.1.0 from the 42.2-RC1 version :-- sysman@toyb:~> scanimage -L device `genesys:libusb:001:005' is a Canon LiDE 110 flatbed scanner sysman@toyb:~> scanimage -T scanimage: sane_start: Invalid argument ______________________ I have now purchased a Canon LiDE 220. This is not recognised by lsusb and there is no entry for it in /etc/sane.d/*.conf. It is recognised in Tumleweed-20161101 lsusb (04a9:190f), but scanimage -T returns an “Error during device I/O”. Other trials with a Canon LiDE 25 were pointless as sane-backends now has no entry for this model (openSUSE-13.2, 42.1, 42.2 or TW) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1005673 http://bugzilla.opensuse.org/show_bug.cgi?id=1005673#c54 --- Comment #54 from Stanislav Brabec --- ray herman: This look like a different bug. In the case reported here, the scanner is recognized, but crashes on scan. Please open a new but report. There is something very strange in your report: /usr/lib64/libusb-1.0.so.0 links to /usr/lib64/libusb-1.0.so.0.1.0 out of the box. Did your replace /usr/lib64/libusb-1.0.so.0.1.0 with an older release? Even then it looks suspicious: You link your libusb-1.0.so.0 to a file that should be eqaul, and things stop to work. It does not make sense to me. Did you reboot between your experiments? Maybe you confused SANE daemon by your experiments. There was no change in libusb-1_0 code since Sep 14 2015 and since Leap 42.1. (Change from May 25 UTC 2016 Update to GNOME 3.20.2 FATE#318572 looks like a fail, the only real change was turning parallel build off.) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1005673 http://bugzilla.opensuse.org/show_bug.cgi?id=1005673#c56 Stanislav Brabec changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(jsmeix@suse.com) --- Comment #56 from Stanislav Brabec --- I just inspectect "git log backend/genesys*". It is a full of fixes. Several of them have a potential to fix particular models at particular resolution. Johannes: What do you think about upgrade of SANE to the git version, or at least upgrade genesys driver? Technically, there are still ways to bisect, but I am not sure whether it will be useful, because git log indicates that different scanners and different resolutions need different fixes: - You can check-out 1.0.24/25, mark it bad, then go back to 1.0.23 to find breaking commit. - You can check 1.0.24/25, mark it bad, and then go forward to HEAD, and find the fixing commit. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1005673 http://bugzilla.opensuse.org/show_bug.cgi?id=1005673#c58 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jsmeix@suse.com) | --- Comment #58 from Johannes Meixner --- Stanislav Brabec, (last week I was not in the office) regarding your question in comment#56 "upgrade of SANE to the git version, or at least upgrade genesys driver": In general see https://en.opensuse.org/SDB:Configuring_Scanners therein the section "RPM packages of the "sane-backends" scanner drivers" that reads (excerpts): ------------------------------------------------------------------------- In general we do not provide unstable "sane-backends" development versions (e.g. Git snapshots) in the "graphics" project which is for developing the openSUSE "sane-backends" RPM package but not for developing scanner drivers. The latter happens upstream at the SANE project. ... In general we (i.e. openSUSE) distribute the "sane-backends" scanner drivers from the SANE project but we do not develop scanner drivers. Usually we do not have all those various kind of scanners for all those various kind of scanner drivers so that usually we cannot do anything when a particular scanner driver does not work. In particular usually we cannot reproduce issues with scanner drivers. When a particular scanner driver ... does not work for you with the currently latest "sane-backends" version that is officially released by the SANE project, then it is recommended to report the issue directly to the driver authors at the SANE project http://www.sane-project.org so that there is a direct communication between you and the upstream authors. ... The best way is to report it on the sane-devel mailing list so that the upstream authors plus interested users can notice the issue, see http://www.sane-project.org/mailing-lists.html ------------------------------------------------------------------------- In particular I do not have a scanner that uses the "genesys" driver. Bottom line: When it is likely an issue in "sane-backends" then please get in direct contact with the the upstream driver authors at the SANE project. Independent of what we do in the OBS "graphics" project, everybody can of course always build any kind of sane-backends development version in his OBS home project. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1005673 http://bugzilla.opensuse.org/show_bug.cgi?id=1005673#c60 --- Comment #60 from Stanislav Brabec --- Very strange! There were no changes in the genesys code in the last 7 days. Only xerox backend was changes. There is probably another condition of scan failure. Do you always try the same resolution and mode? The changelog indicates that different resolutions need different fixes. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1005673 http://bugzilla.opensuse.org/show_bug.cgi?id=1005673#c62 Bit Juggler changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #62 from Bit Juggler --- Because i thought i might have messed up my openSUSE 42.2 RC2 installation by all my tests i did a clean, new installation yesterday using http://download.opensuse.org/distribution/leap/42.2-RC2/iso/openSUSE-Leap-42.... After that i did "zypper dup" to get the latest fixes from the update repository and checked the software versions of SANE, LIBUSB and KERNEL: sane-backends 1.0.24-4.40 sane-backends-autoconfig 1.0.24-4.40 libusb-0_1-4 0.1.13-32.4 libusb-1_0-0 1.0.20-3.4 libusbmuxd4 1.0.10-4.2 kernel-default 4.4.27-2.1 And then i ran the tests described in Comment #61. The result was: EVERYTHING WORKS FINE !!! Compared to the original software setup (from Comment #1) the only changes i can see are SANE moved from 1.0.24-4.39 to 1.0.24-4.40 I do not understand what happened but i guess the problem is solved. Thank you all for your help! -- You are receiving this mail because: You are on the CC list for the bug.