https://bugzilla.novell.com/show_bug.cgi?id=697694 https://bugzilla.novell.com/show_bug.cgi?id=697694#c zj jia <zjjia@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zjjia@novell.com AssignedTo|bnc-team-screening@forge.pr |yast2-maintainers@suse.de |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=697694 https://bugzilla.novell.com/show_bug.cgi?id=697694#c2 Hendrik Woltersdorf <hendrikw@arcor.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|hendrikw@arcor.de | --- Comment #2 from Hendrik Woltersdorf <hendrikw@arcor.de> 2011-06-14 15:52:40 UTC --- Created an attachment (id=434366) --> (http://bugzilla.novell.com/attachment.cgi?id=434366) Yast2-logs -- 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=697694 https://bugzilla.novell.com/show_bug.cgi?id=697694#c3 Johannes Meixner <jsmeix@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsmeix@novell.com Component|YaST2 |Other AssignedTo|jsmeix@novell.com |bnc-team-screening@forge.pr | |ovo.novell.com Summary|yast scanner module |autodetecting USB scanners |disables usb mouse |disables USB mouse QAContact|jsrain@novell.com |qa@suse.de --- Comment #3 from Johannes Meixner <jsmeix@novell.com> 2011-06-15 07:34:09 UTC --- The root cause is not the YaST sanner module itself. The YaST sanner module runs standard tools to autodetect scanners via the bash script /usr/lib/YaST2/bin/autodetect_scanners In particular it runs sane-find-scanner -q and hp-probe -busb -escan Run them both as root to find out which of those tools disables your USB mouse. Then inspect /var/log/messages only during the time when those tools run for suspicious messages related to USB and post those messages here. For openSUSE 12.1 those tools did not change. Therefore the root cause is likely lower-level USB probably kernel (compare bug #699450) or perhaps udev or something like this. -- 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=697694 https://bugzilla.novell.com/show_bug.cgi?id=697694#c4 Hendrik Woltersdorf <hendrikw@arcor.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|hendrikw@arcor.de | --- Comment #4 from Hendrik Woltersdorf <hendrikw@arcor.de> 2011-06-15 18:01:07 UTC --- I started the two tools and the Yast script as root: ---------------------------------------------------------------------------- lthendrik:/home/hendrik # sane-find-scanner -q lthendrik:/home/hendrik # hp-probe -busb -escan warning: hp-probe should not be run as root/superuser. HP Linux Imaging and Printing System (ver. 3.11.5) Printer Discovery Utility ver. 4.1 Copyright (c) 2001-9 Hewlett-Packard Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. -------------------- | DEVICE DISCOVERY | -------------------- warning: No devices found on the 'usb' bus. If this isn't the result you are expecting, warning: check to make sure your devices are properly connected and powered on. Done. lthendrik:/home/hendrik # /usr/lib/YaST2/bin/autodetect_scanners warning: hp-probe should not be run as root/superuser. warning: No devices found on the 'usb' bus. If this isn't the result you are expecting, warning: check to make sure your devices are properly connected and powered on. warning: hp-probe should not be run as root/superuser. warning: No devices found on the 'cups' bus. If this isn't the result you are expecting, warning: check to make sure your devices are properly connected and powered on. CONNECTION|DEVICE|MANUFACTURER|USB_VENDOR_ID|MODEL|USB_PRODUCT_ID|DESCRIPTION lthendrik:/home/hendrik # -------------------------------------------------------------------------------- the message log of that time: Jun 15 19:47:54 lthendrik hp-probe: hp-probe[8158]: warning: hp-probe should not be run as root/superuser. Jun 15 19:47:54 lthendrik hp-probe: hp-probe[8158]: warning: No devices found on the 'usb' bus. If this isn't the result you are expecting, Jun 15 19:47:54 lthendrik kernel: [ 421.171101] hp-probe[8158]: hp-probe[8158]: warning: check to make sure your devices are properly connected and powered on. Jun 15 19:48:07 lthendrik hp-probe: hp-probe[8172]: warning: hp-probe should not be run as root/superuser. Jun 15 19:48:07 lthendrik hp-probe: hp-probe[8172]: warning: No devices found on the 'usb' bus. If this isn't the result you are expecting, Jun 15 19:48:07 lthendrik hp-probe: hp-probe[8172]: warning: check to make sure your devices are properly connected and powered on. Jun 15 19:48:09 lthendrik hp-probe: hp-probe[8184]: warning: hp-probe should not be run as root/superuser. Jun 15 19:48:09 lthendrik hp-probe: hp-probe[8184]: warning: No devices found on the 'cups' bus. If this isn't the result you are expecting, Jun 15 19:48:09 lthendrik hp-probe: hp-probe[8184]: warning: check to make sure your devices are properly connected and powered on. ------------------------------------------------------------------------- None of these tools disabled my USB mouse. So I started the GUI-Yast2-scanner module and than the mouse got disabled. The message log of that try: Jun 15 19:49:43 lthendrik hp-probe: hp-probe[8489]: warning: hp-probe should not be run as root/superuser. Jun 15 19:49:43 lthendrik hp-probe: hp-probe[8489]: warning: No devices found on the 'usb' bus. If this isn't the result you are expecting, Jun 15 19:49:43 lthendrik hp-probe: hp-probe[8489]: warning: check to make sure your devices are properly connected and powered on. Jun 15 19:49:44 lthendrik hp-probe: hp-probe[8497]: warning: hp-probe should not be run as root/superuser. Jun 15 19:49:44 lthendrik hp-probe: hp-probe[8497]: warning: No devices found on the 'cups' bus. If this isn't the result you are expecting, Jun 15 19:49:44 lthendrik hp-probe: hp-probe[8497]: warning: check to make sure your devices are properly connected and powered on. Jun 15 19:49:56 lthendrik hp-probe: hp-probe[8529]: warning: hp-probe should not be run as root/superuser. Jun 15 19:49:56 lthendrik hp-probe: hp-probe[8529]: warning: No devices found on the 'usb' bus. If this isn't the result you are expecting, Jun 15 19:49:56 lthendrik hp-probe: hp-probe[8529]: warning: check to make sure your devices are properly connected and powered on. Jun 15 19:49:57 lthendrik hp-probe: hp-probe[8537]: warning: hp-probe should not be run as root/superuser. Jun 15 19:49:57 lthendrik hp-probe: hp-probe[8537]: warning: No devices found on the 'cups' bus. If this isn't the result you are expecting, Jun 15 19:49:57 lthendrik hp-probe: hp-probe[8537]: warning: check to make sure your devices are properly connected and powered on. -- 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=697694 https://bugzilla.novell.com/show_bug.cgi?id=697694#c6 Johannes Meixner <jsmeix@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |hendrikw@arcor.de --- Comment #6 from Johannes Meixner <jsmeix@novell.com> 2011-06-16 10:20:30 UTC --- Does # scanimage -L make your USB mouse disabled when there is no scanner configured? Details: If I understand correctly what you wrote in comment #0 "When I start the scanner module in YaST2 my USB mouse does not work anymore" you mean that your USB mouse gets disabled while the YaST scanner module starts up - i.e. your USB mouse is already disabled when the YaST scanner module shows its initial "Scanner Configuration" dialog. This are the scripts which the YaST scanner module runs while it starts up: # /usr/lib/YaST2/bin/create_scanner_database YCP # /usr/lib/YaST2/bin/determine_active_scanners YCP # /usr/lib/YaST2/bin/determine_active_scanner_backends YCP # /usr/lib/YaST2/bin/autodetect_scanners YCP See the output of # grep 'Scanner\.ycp:.*Executing bash commandline:' /var/log/YaST2/y2log Run those scripts one after the other as root as follows: # /usr/lib/YaST2/bin/create_scanner_database YCP &>/dev/null # /usr/lib/YaST2/bin/determine_active_scanners YCP &>/dev/null # /usr/lib/YaST2/bin/determine_active_scanner_backends YCP &>/dev/null # /usr/lib/YaST2/bin/autodetect_scanners YCP &>/dev/null and after each, check if your USB mouse was disabled. Once you found the script which makes your USB mouse disabled, inspect it to see the actual command which is executed therein which makes your USB mouse disabled. I guess it is perhaps the command # scanimage -f '%d,%v,%m;' in /usr/lib/YaST2/bin/determine_active_scanners which is equivalent to # scanimage -L -- 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=697694 https://bugzilla.novell.com/show_bug.cgi?id=697694#c8 Johannes Meixner <jsmeix@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |ASSIGNED Component|Other |YaST2 Platform|i686 |All AssignedTo|bnc-team-screening@forge.pr |jsmeix@novell.com |ovo.novell.com | QAContact|qa@suse.de |jsrain@novell.com Summary|autodetecting USB scanners |yast2-scanner: run |disables USB mouse |autodetect_scanners | |subsequently could lead to | |disabled USB devices (e.g. | |USB mouse) OS/Version|Other |SuSE Other --- Comment #8 from Johannes Meixner <jsmeix@novell.com> 2011-06-17 08:38:18 UTC --- Very many thanks for your analysis! Such good analysis help us so much! In yast2-scanner I like to add some artificial sleep time between subsequent calls of autodetect_scanners hoping that this helps to avoid the issue. Please add a "sleep 3" line in /usr/lib/YaST2/bin/autodetect_scanners before each of the "sane-find-scanner -q" and "hp-probe -busb -escan" calls as follows: ----------------------------------------------------------------- if [ -x /usr/bin/sane-find-scanner ] then sleep 3 sane-find-scanner -q >$TMP_DATA_RAW & .. if [ -x /usr/bin/hp-probe ] then sleep 3 hp-probe -busb -escan | tr -s '[:blank:]' | grep ... ----------------------------------------------------------------- Then again run "/usr/lib/YaST2/bin/autodetect_scanners YCP" a couple of times at the command line directly one after another. Please report which sleep value works well for you (perhaps "sleep 1" is already sufficient, or you may need even "sleep 10"). The root cause is a low-level timing problem probably somehow related to lower-level USB (i.e. kernel) or perhaps udev or something like this. YaST does not run the programs simultaneously but one after the other and even if such programs would run simultaneously no USB device should get disabled. On a multi-tasking/mulit-user system, it should work when all users run "sane-find-scanner -q" and/or "hp-probe -busb -escan" many times simultaneously. Please try out if running "sane-find-scanner -q" many times or running "hp-probe -busb -escan" many times makes your USB mose disabled. Then I suggest that you make a new separate bug report (probably regarding "kernel") where you describe only the root issue - e.g. something like "running <USB-scanning-program> leads to disabled 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=697694 https://bugzilla.novell.com/show_bug.cgi?id=697694#c9 Hendrik Woltersdorf <hendrikw@arcor.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|hendrikw@arcor.de | --- Comment #9 from Hendrik Woltersdorf <hendrikw@arcor.de> 2011-06-17 18:34:54 UTC --- I tested the two programs and found, that sane-find-scanner is the program disabling my mouse. But waiting <n> seconds does not solve the problem. Sometimes even the first run after waiting a minute or longer disables the mouse. Should I open a new bug here (regarding "kernel") or at the SANE bug tracker at debian.org? -- 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=697694 https://bugzilla.novell.com/show_bug.cgi?id=697694#c11 --- Comment #11 from Hendrik Woltersdorf <hendrikw@arcor.de> 2011-06-21 18:13:23 UTC --- I opened a kernel bug report for this case: #701368. -- 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.