[Bug 155142] The keyboard stops responding except for repeats

[Erik Anderson]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=155142         




------- Additional Comments From erikanderson3 gmail com  2008-01-08 18:00 -------
I find the same with Kubuntu Gutsy, running on a stock Dell Dimension 5150 desktop.  In my case, the keyboard will sometimes quit responding at all except for Ctrl commands, but *only* for the specific app, and generally (maybe always, not sure) after using a keyboard shortcut to do something.

Examples:
* Using my custom Win+T command to open a Konsole terminal sometimes (but not always) results in the keyboard not working for that terminal session.  
* Using R to reply in Kontact's KMail, or Ctrl+N for a new message / to-do / calendar item sometimes (but not always) results in Kontact ignoring all keyboard input in text fields (Ctrl commands like Ctrl+Q to quit and other keyboard shortcuts like R for reply still function).
* Konqueror sometimes also begins to completely ignore the keyboard (except for Ctrl commands) in text input areas like the Google bar or address bar, generally after some keyboard shortcut is used.

In all cases, the mouse continues to operate just fine, it's just that text cannot be typed into any text fields.  Sometimes repeatedly hitting the keyboard seems to have an effect, but sometimes not.  Perhaps a QT problem?  Text can be *pasted* in, but this is not an acceptable workaround.  Closing the offending app and reopening seems to reset the problem, and the keyboard will function ordinarily again.  So far I have only observed the problem in KDE apps; I have never seen this with Firefox, for instance.  

I do not have Gnome installed, so I cannot presently check if this occurs there.  My file server is Xubuntu 7.04, and I've never seen this issue there.  Kubuntu 7.10 is my first Kubuntu install, but it's interesting to note Vivien's 7.04 issue.  Given the symptoms, my shot-in-the-dark guess is that it's some sort of weird QT widget race condition.