Update seems to have stopped Xorg talking to mouse and keyboard in Multiseat
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
multiseat |
Invalid
|
Undecided
|
Unassigned | ||
nvidia-graphics-drivers-180 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I'm using fully up to date Jaunty (28/2/09) configured with MDM (http://
A update this week, between Monday and about Wednesday/Thursday seems to have made the underlying X server Display:0 stop receiving input events from the mouse and the keyboard.
The nested Xephyr sessions (Displays :1 to :4) running on top of Display:0 still work fine. This proves that the keyboards and mice are still being detected and passing events through to the Xephyr sessions correctly.
This regression or change in behaviour was first noticed by the fact that xorg goes into power saving due to inactivity and then cannot be woken up. Its also seen by the fact you can't change VT's anymore and keyboard LED's don't work.
What do I expect to happen
The underlying Xserver Display:0 receives events from the keyboards and mice so it can still turn the keyboard LED's on and off. It will also not go into power saving if it detects activity on any of the attached keyboards and mice.
What actually happens
The underlying Xserver Display:0 appears as if no keyboard and mice events are being generated, even though they can be seen to be working in Xephyr sessions running on top of it.
Changed in multiseat: | |
status: | New → Invalid |
Changed in xorg (Ubuntu): | |
status: | Incomplete → New |
Changed in nvidia-graphics-drivers-180 (Ubuntu): | |
status: | Incomplete → Fix Released |
Not enough information to troubleshoot. See http:// wiki.ubuntu. com/X/Reporting for instructions on reporting X issues and https:/ /wiki.ubuntu. com/X/Troublesh ooting/ HalBreaksKeyboa rdAndMouse and please provide additional details.