REGRESSION: USB mouse & keyboard don't work immediatly on login
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-device-manager (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
My Microsoft non-wireless mouse & keyboard worked perfectly on jaunty (9.04), until I installed all the latest updates last friday (2009-06-19). Those new updates of a little over 2 weeks old, included a kernell update it seems, because ubuntu had to restart.
Since then, 2 major regressions are introduced:
- the startup takes a lot longer. At some point the ubuntu logo dissappears and I get console messages about USB. It prints one, has a certain time out, then prints the next and so on, 8 times in general (4 for each device I think)
- both the USB mouse and keyboard don't work immediately in the login screen. After the login screen is shown for about a minute, they all of a sudden start working.
Unplugging the mouse and keyboard and plugin them in when the login screen is visible, is a (although annoying) workaround.
During shutdown the ubuntu logo dissappears again and I get these messages:
usb 5-1: device description read/64 error -110
usb 5-1: device description read/64 error -110
usb 5-1: device description read/64 error -110
usb 5-1: device description read/64 error -110
usb 5-1: device description read/8 error -110
usb 5-1: device description read/8 error -110
usb 5-1: device description read/8 error -110
usb 5-1: device description read/8 error -110
I had exactly the same problem on my old pc, with the same Microsoft USB mouse on ubuntu 8.04. I figured Ubuntu 8.10 and later finally fixed it once and for all.
Even if there is some magical command to fix my problem today, the update shouldn't cause this problem and it should be ensured (through unit tests or something) that it doesn't happen again on the next update.
Normal users are not able to find and run such magical commands, nor are they tolerant to such regressions upon installing updates.
What files do I need to attach to this issue so you can decently evaluate this issue?
xorg.conf hasn't been changed since 2009-04-25, so the regression update of 2009-06-19 didn't change it.