From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003
Description of problem:
Red Hat 8.0 introduced an extra USB mouse that is configured by default in
XF86Config. This has been very convenient for laptop users with PS/2 touchpads
and hotpluggable USB mouse. This dual mouse operation works great with only one
During system bootup, kudzu sees that the USB mouse has been added or removed
and attempts to reconfigure the mouse, running text mode "mouseconfig". This
can be confusing to less experienced users since mouse configuration does not
need to change.
I propose that minor modifications be made to kudzu so it will know when to
ignore changes in the optional USB mouse. Perhaps kudzu could check a flag set
by redhat-config-mouse (or the Anaconda equivalent) in /etc/sysconfig.
Steps to Reproduce:
1. Setup laptop with PS/2 mouse, optional USB mouse is configured.
2. Plug or unplug USB mouse before kudzu during bootup.
Kudzu asks you to reconfigure the mouse. Potential end user confusion.
It should ignore the adding/removing the USB mouse since it is optional and
Another equally annoying problem is that Kudzu will run at boot when alternating
a laptop between docking staticn connect and disconnect. On my Dell Latitude
C610, it will step the user through USB hub detection/removal, ethernet
The same proposed solution would be nice for these sorts of peripherals as well.
Recently introduced in Rawhide was some behavior in either kudzu or
redhat-config-mouse that made the situation a bit worse. Now when booting,
kudzu detects the new USB mouse, if you choose "Configure" it configures without
going into the text-mode mouse configuration tool. Getting rid of the mouse
configuration tool was good, however it automatically configured the USB mouse
as if it were the only mouse, rendering the PS/2 touchpad disabled.
I'm not entirely sure if this is in kudzu or redhat-config-mouse, which
component should I file this under?
kudzu is now calling redhat-config-mouse with the same arguments that it used to
call the old mouseconfig. We might want to check to see how it's handling this.
Fixed in 0.99.97; it now does not configure newly found USB mice, as they're
Should I file a separate RFE for comment #1?
There's already a bug on handling docking stations. Not sure what a good way to
do it is, though.
*** Bug 71970 has been marked as a duplicate of this bug. ***