Bug 185890 - Keyboard input suddenly stops working (KDE)
Summary: Keyboard input suddenly stops working (KDE)
Status: RESOLVED DUPLICATE of bug 193083
Alias: None
Product: khotkeys
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Michael Jansen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-01 18:23 UTC by gmud
Modified: 2009-05-19 05:06 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description gmud 2009-03-01 18:23:33 UTC
Version:           Unbekannt (using 4.2.00 (KDE 4.2.0), Kubuntu packages)
Compiler:          cc 
OS:                Linux

I am unable to offer exact steps to reproduce.
Description:

The keyboard input suddenly stops working in all KDE applications (thus making the whole session unusable). There are no error messages, neither in /var/log/messages nore in .xsession-errors or kdm-log or anywhere else I could look with only the mouse working. Interestingly the virtual keyboard does not work, too. This also explains that if I connect a USB keyboard to my notebook it shows up correctly in /var/log/messages but it doesn't change the situation in the current kde session. I first though it may be a hardware error, but when I logged off from KDE, I was able to switch to another terminal with ctrl-alt-f? . 

I also noticed that this happens when I quickly change windows mit the alt-tab combination. I have had this problem about 5 times since now.

Sorry that I cannot deliver a better reproduable report. If I would know what of QT or KDE is responsible for handling keyboard input I would try to hunt the bug down...
Comment 1 A. Spehr 2009-05-19 05:04:47 UTC
See comments #56 and #57 for workarounds.

*** This bug has been marked as a duplicate of bug 171685 ***
Comment 2 A. Spehr 2009-05-19 05:06:51 UTC
Actually, this one is a better fit. The workarounds still might work.

*** This bug has been marked as a duplicate of bug 193083 ***