Description of problem:
There are some problems with switching from VT1 to VT2 when ctrl and alt buttons aren't released.
Version-Release number of selected component (if applicable):
LiveCD distribution testday-20090909-x86_64.iso.
Steps to Reproduce:
ctrl+alt+F2 does't work in the following workflow:
- press ctrl+alt+F2 and release only F2 button, ctrl and alt should remain pressed - the system switches to the second virtual terminal.
- then press F1 and again don't release ctrl and alt - the system switches to the first virtual terminal.
- then press F2 - the system doesn't switch to the second virtual terminal, it's a BUG.
ctrl+alt+F2 doesn't work.
ctrl+alt+F2 should switch the system to VT2.
Motherboard: Asus M3A-H/HDMI
Video: ATI Radeon HD3200 GPU (Integrated).
reassigning to server.
The current architecture makes this quite difficult.
Key repeats are triggered in the server only, the driver only forwards actual key presses and key releases*. When you VT switch and come back, the server doesn't know if a key is still down until the next event _for this key_ comes. Changing this would require that the server - after coming back from the VT switch - pokes the driver to query the state of the keyboard, then update the internal state accordingly.
Given the work required to implement this and the limited practical benefit I doubt this will be implemented (or even accepted upstream) anytime soon. I'll have to close this as WONTFIX, sorry.
* not quite true for kbd, but evdev is the default these days.