Comment 317 for bug 124406
Revision history for this message
| james_mcl (james-d-mclaughlin-googlemail) wrote | #317 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
In answer to post 310, Bryce, I'm sorry but there's a serious misunderstanding of the issue in your post.
You state "hitting a key a second time (to fire a new up-key signal) makes things work."
This is not the case for everyone affected, or for every instance of the bug. The original poster, and post 121, refer to subsequent keypresses and their keydown events being ignored completely by the system. Post 40 mentions the need to "furiously" press another key several times to get the system to recognise it and stop the repeats.
In my case, the behaviour of the bug has varied as I've gone through different distros; possibly not behaving consistently even in identical distros (since my workaround for the past two-and-a-half years has been to go back to Hardy Heron, this hasn't really been put to the test.)