https://bugzilla.novell.com/show_bug.cgi?id=701368 https://bugzilla.novell.com/show_bug.cgi?id=701368#c2 --- Comment #2 from Hendrik Woltersdorf 2011-08-14 18:31:51 UTC --- Today I retested this with the current factory versions, that should be openSUSE 12.1 Milestone 4. sane: sane-backends-1.0.22-13.6.i586 kernel: Linux lthendrik.site 3.0.0-2-desktop #1 SMP PREEMPT Fri Jul 22 08:28:15 UTC 2011 (50c05d7) i686 i686 i386 GNU/Linux The issue with the mouse still exists. I tested with two other USB devices, an external hard disk and a DVB-T-stick. Both devices keep working, when the mouse gets blocked. hwinfo --mouse shows this about that USB mouse: lthendrik:/home/hendrik # hwinfo --mouse 39: USB 00.0: 10503 USB Mouse [Created at usb.122] Unique ID: FKGF.IvHLBRRchEC Parent ID: pBe4.v+N+B0xY+P6 SysFS ID: /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0 SysFS BusID: 2-1:1.0 Hardware Class: mouse Model: "STMicroelectronics Imaging Division (VLSI Vision) 5 button optical mouse with scroll wheel" Hotplug: USB Vendor: usb 0x0553 "STMicroelectronics Imaging Division (VLSI Vision)" Device: usb 0x0a02 "5 button optical mouse with scroll wheel" Revision: "1.00" Compatible to: int 0x0210 0x0015 Driver: "usbhid" Driver Modules: "usbhid" Device File: /dev/input/mice (/dev/input/mouse0) Device Files: /dev/input/mice, /dev/input/mouse0, /dev/input/event1, /dev/input/by-id/usb-5_button_optical_mouse_with_scroll_wheel_5_button_optical_mouse_with_scroll_wheel-event-mouse, /dev/input/by-path/pci-0000:00:1d.0-usb-0:1:1.0-event-mouse, /dev/input/by-id/usb-5_button_optical_mouse_with_scroll_wheel_5_button_optical_mouse_with_scroll_wheel-mouse, /dev/input/by-path/pci-0000:00:1d.0-usb-0:1:1.0-mouse Device Number: char 13:63 (char 13:32) Speed: 1.5 Mbps Module Alias: "usb:v0553p0A02d0100dc00dsc00dp00ic03isc01ip02" Driver Info #0: Buttons: 5 Wheels: 1 XFree86 Protocol: explorerps/2 GPM Protocol: exps2 Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #35 (Hub) -- 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=701368 https://bugzilla.novell.com/show_bug.cgi?id=701368#c Jeff Mahoney changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel-maintainers@forge.pr |oneukum@suse.com |ovo.novell.com | -- 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=701368 https://bugzilla.novell.com/show_bug.cgi?id=701368#c5 Hendrik Woltersdorf changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|hendrikw@arcor.de | --- Comment #5 from Hendrik Woltersdorf 2012-03-07 18:22:03 UTC --- Created an attachment (id=480136) --> (http://bugzilla.novell.com/attachment.cgi?id=480136) new system logs from sane-find-scanner runs I reinstalled OS 12.1 at the test machine, and let sane-find-scanner run until the mouse got blocked. Another run of sane-find-scanner unblocked the mouse. After that I copied /var/log/messages und the output of dmesg. -- 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=701368 https://bugzilla.novell.com/show_bug.cgi?id=701368#c7 Hendrik Woltersdorf changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|hendrikw@arcor.de | --- Comment #7 from Hendrik Woltersdorf 2012-03-08 19:42:26 UTC --- Created an attachment (id=480498) --> (http://bugzilla.novell.com/attachment.cgi?id=480498) lsusb output I attached the output of lsusb -v before and after the mouse got blocked by sane-find-scanner. -- 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=701368 https://bugzilla.novell.com/show_bug.cgi?id=701368#c9 Hendrik Woltersdorf changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|hendrikw@arcor.de | --- Comment #9 from Hendrik Woltersdorf 2012-03-09 18:19:42 UTC --- Created an attachment (id=480769) --> (http://bugzilla.novell.com/attachment.cgi?id=480769) lsusb -t output -- 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=701368 https://bugzilla.novell.com/show_bug.cgi?id=701368#c11 Oliver Neukum changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |hendrikw@arcor.de --- Comment #11 from Oliver Neukum 2012-03-21 09:17:47 UTC --- (In reply to comment #10)

Created an attachment (id=480771) --> (http://bugzilla.novell.com/attachment.cgi?id=480771) [details] lsusb -D output

One more try with: lsusb -D /dev/bus/usb/003/002 There is a difference.

I am afraid I am too stupid to see it. Could you clarify? -- 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=701368 https://bugzilla.novell.com/show_bug.cgi?id=701368#c13 Oliver Neukum changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |hendrikw@arcor.de --- Comment #13 from Oliver Neukum 2012-03-26 10:19:33 UTC --- (In reply to comment #3)

More versions, more tests:

openSUSE 12.1 Final : bug still there openSUSE 12.1 Final with Tumbleweed (kernel 3.2): bug still there

openSUSE 12.2 Milestone 1: bug is gone

Very well. Could you try the kernel of the working version 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.

https://bugzilla.novell.com/show_bug.cgi?id=701368 https://bugzilla.novell.com/show_bug.cgi?id=701368#c15 Oliver Neukum changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |hendrikw@arcor.de --- Comment #15 from Oliver Neukum 2012-04-17 12:54:00 UTC --- (In reply to comment #14)

versions and found in the 12.2-version an error message: "libusb not available"

This is odd due to a kernel change. Please check for the availability of libusb with the rpm tool. -- 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=701368 https://bugzilla.novell.com/show_bug.cgi?id=701368#c17 Oliver Neukum changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |jsmeix@suse.com --- Comment #17 from Oliver Neukum 2012-04-18 08:07:02 UTC --- Johannes, this suggests strongly that this is a problem with the firmware of the mouse in question. Can we teach sane-find-scanner to leave such devices alone? Is there a scanner that pretends to be an HID device? -- 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=701368 https://bugzilla.novell.com/show_bug.cgi?id=701368#c19 Hendrik Woltersdorf changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|hendrikw@arcor.de | --- Comment #19 from Hendrik Woltersdorf 2012-04-18 16:30:15 UTC --- Created an attachment (id=486731) --> (http://bugzilla.novell.com/attachment.cgi?id=486731) output of sane-findscanner -v -v -- 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=701368 https://bugzilla.novell.com/show_bug.cgi?id=701368#c21 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|jsmeix@suse.com | --- Comment #21 from Johannes Meixner 2012-04-19 09:39:21 UTC --- There are two check_libusb_device functions in tools/sane-find-scanner.c in the SANE sources, one "#ifdef HAVE_LIBUSB" and one "#ifdef HAVE_LIBUSB_1_0". As far as I see the check_libusb_device functions only test libusb values and does not communicate with the USB device (long lines shown wrapped here): ------------------------------------------------------------------------------ #ifdef HAVE_LIBUSB ... for (interface_nr = 0; interface_nr < dev->config[0].bNumInterfaces && is_scanner <= 0; interface_nr++) { switch (dev->descriptor.bDeviceClass) { case USB_CLASS_VENDOR_SPEC: ++is_scanner; break; case USB_CLASS_PER_INTERFACE: if (dev->config[0].interface[interface_nr].num_altsetting == 0 || !dev->config[0].interface[interface_nr].altsetting) break; switch (dev->config[0].interface[interface_nr].altsetting[0].bInterfaceClass) { case USB_CLASS_VENDOR_SPEC: case USB_CLASS_PER_INTERFACE: case 16: /* data? */ ++is_scanner; break; } break; } } if (is_scanner > 0) { char * chipset = check_usb_chip (dev, verbose, from_file); printf ("found USB scanner (vendor=0x%04x", dev->descriptor.idVendor); ... #ifdef HAVE_LIBUSB_1_0 ... for (intf = 0; (intf < config0->bNumInterfaces) && (is_scanner <= 0); intf++) { switch (desc.bDeviceClass) { case USB_CLASS_VENDOR_SPEC: ++is_scanner; break; case USB_CLASS_PER_INTERFACE: if ((config0->interface[intf].num_altsetting == 0) || config0->interface[intf].altsetting) break; switch (config0->interface[intf].altsetting[0].bInterfaceClass) { case USB_CLASS_VENDOR_SPEC: case USB_CLASS_PER_INTERFACE: case 16: /* data? */ ++is_scanner; break; } break; } } ... if (is_scanner > 0) { #if 0 char *chipset = check_usb_chip (dev, verbose, from_file); #endif printf ("found USB scanner (vendor=0x%04x", vid); ------------------------------------------------------------------------------ where include/sane/sanei_usb.h lists ------------------------------------------------------------------------ #define USB_CLASS_VENDOR_SPEC 0xff #define USB_CLASS_PER_INTERFACE 0x00 ------------------------------------------------------------------------ As far as I see sane-find-scanner only does check_usb_chip when the USB device class is 255 "Vendor Specific Class" and then it would print "found USB scanner" which is not the case in attachment #486731 Therefore - from my point of view - there is no code in sane-find-scanner which can trigger that the "5 button optical mouse with scroll wheel" gets disconnected. But I am not at all an USB expert so that my analysis could be wrong. -- 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=701368 https://bugzilla.novell.com/show_bug.cgi?id=701368#c23 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED InfoProvider|jsmeix@suse.com | Resolution| |WONTFIX Summary|running sane-find-scanner |Particular USB mouse gets |leads to disabled USB |disabled when finding USB |device (mouse) |devices via libusb (e.g. by | |running sane-find-scanner) --- Comment #23 from Johannes Meixner 2012-04-19 13:36:01 UTC --- As far as I see in the SANE sources for the sanei_usb_init function in sanei/sanei_usb.c it calls the libusb functions usb_init(); usb_find_busses(); usb_find_devices (); before it loops through all of the busess and all of the devices to find USB devices with "USB_CLASS_VENDOR_SPEC": ----------------------------------------------------------------------- sanei_usb_init ... DBG (4, "sanei_usb_init: Looking for libusb devices\n"); usb_init (); #ifdef DBG_LEVEL if (DBG_LEVEL > 4) usb_set_debug (255); #endif /* DBG_LEVEL */ usb_find_busses (); usb_find_devices (); /* Check for the matching device */ for (bus = usb_get_busses (); bus; bus = bus->next) { for (dev = bus->devices; dev; dev = dev->next) { ----------------------------------------------------------------------- Hendrik Woltersdorf, you could run ------------------------------------------------ # export SANE_DEBUG_SANEI_USB=128 # sane-find-scanner -v -v 2>&1 | less ------------------------------------------------ to get additionally SANE USB debug messages. Check for "Looking for libusb devices" and subsequent messages. I.e. SANE works - as far as I see - as described in http://libusb.sourceforge.net/doc/examples-code.html I assume this particular "5 button optical mouse with scroll wheel" USB devices would get disconnected when any program calls the libusb functions usb_init(); usb_find_busses(); usb_find_devices(); I do not understand how blacklisting in SANE could help at all when a device get disconnected when the libusb functions usb_init(); usb_find_busses(); usb_find_devices(); are called because those functions are not device specific. Therefore I think a blacklist for broken USB devices which get disconnected when those libusb functions are called as described in the libusb Developers Guide might work if it happens in libusb to avoid such issues for any program and not only for SANE programs. On the other hand: If a broken USB device would be blacklisted in libusb (so that libusb ignores it), how could it be used at all? In the end I think blacklisting would not really help (at least not in SANE). As far as I see all what Hendrik Woltersdorf could do with his "5 button optical mouse with scroll wheel" is to re-plug it whenever it got disconnected. I will ask on the sane-devel@lists.alioth.debian.org mailing list what SANE upstream thinks about blacklisting USB devices in SANE because in other exceptional cases it might make sense. I close the issue as WONTFIX for openSUSE which means that we (i.e. openSUSE) will not (and probably cannot) implement something to work around such broken USB devices. -- 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=701368 https://bugzilla.novell.com/show_bug.cgi?id=701368#c26 --- Comment #26 from Hendrik Woltersdorf 2012-04-20 19:40:25 UTC --- I tested the sane-backends from the "graphics" repository. Now things got worse. When the mouse got disabled, that disabled state survived a reboot. I needed to plug in a different mouse (Logitech M90), which worked. After that the "problem-mouse" did work again. See the corresponding dmesg output: ... [ 91.682054] usb 2-1: new low-speed USB device number 6 using uhci_hcd [ 91.847053] usb 2-1: device descriptor read/64, error -71 [ 92.061064] usb 2-1: device descriptor read/64, error -71 [ 92.264067] usb 2-1: new low-speed USB device number 7 using uhci_hcd [ 92.429069] usb 2-1: device descriptor read/64, error -71 [ 92.643024] usb 2-1: device descriptor read/64, error -71 [ 92.846082] usb 2-1: new low-speed USB device number 8 using uhci_hcd [ 93.254079] usb 2-1: device not accepting address 8, error -71 [ 93.356085] usb 2-1: new low-speed USB device number 9 using uhci_hcd [ 93.764078] usb 2-1: device not accepting address 9, error -71 [ 93.764097] hub 2-0:1.0: unable to enumerate USB device on port 1 [ 109.126051] usb 3-2: new low-speed USB device number 2 using uhci_hcd [ 109.291047] usb 3-2: device descriptor read/64, error -71 [ 109.505052] usb 3-2: device descriptor read/64, error -71 [ 109.708062] usb 3-2: new low-speed USB device number 3 using uhci_hcd [ 109.822062] usb 3-2: device descriptor read/64, error -71 [ 110.087075] usb 3-2: device descriptor read/64, error -71 [ 110.290104] usb 3-2: new low-speed USB device number 4 using uhci_hcd [ 110.699045] usb 3-2: device not accepting address 4, error -71 [ 110.801084] usb 3-2: new low-speed USB device number 5 using uhci_hcd [ 111.209079] usb 3-2: device not accepting address 5, error -71 [ 111.209099] hub 3-0:1.0: unable to enumerate USB device on port 2 [ 204.306086] usb 2-1: new low-speed USB device number 10 using uhci_hcd [ 204.520139] usb 2-1: New USB device found, idVendor=046d, idProduct=c05a [ 204.520149] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 204.520156] usb 2-1: Product: USB Optical Mouse [ 204.520162] usb 2-1: Manufacturer: Logitech [ 204.538700] input: Logitech USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0/input/input10 [ 204.539000] generic-usb 0003:046D:C05A.0001: input,hidraw0: USB HID v1.11 Mouse [Logitech USB Optical Mouse] on usb-0000:00:1d.0-1/input0 [ 221.454121] usb 2-1: USB disconnect, device number 10 [ 231.156087] usb 2-1: new low-speed USB device number 11 using uhci_hcd [ 231.384142] usb 2-1: New USB device found, idVendor=0553, idProduct=0a02 [ 231.384151] usb 2-1: New USB device strings: Mfr=1, Product=3, SerialNumber=0 [ 231.384159] usb 2-1: Product: 5 button optical mouse with scroll wheel [ 231.384166] usb 2-1: Manufacturer: 5 button optical mouse with scroll wheel [ 231.403083] input: 5 button optical mouse with scroll wheel 5 button optical mouse with scroll wheel as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0/input/input11 [ 231.403626] generic-usb 0003:0553:0A02.0002: input,hidraw0: USB HID v1.10 Mouse [5 button optical mouse with scroll wheel 5 button optical mouse with scroll wheel] on usb-0000:00:1d.0-1/input0 -------------------------------------------- I tried two times in different ports the problem-mouse before using the Logitech model. -------------------------------------------- lthendrik:/home/hendrik # rpm -qa sane-backends sane-backends-1.0.22-72.1.i586 -- 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.