[Bug 171685] keyboard stops working in kde

Jan Kusanagi akarikusanagi at gmail.com
Fri Nov 13 14:56:52 GMT 2009


https://bugs.kde.org/show_bug.cgi?id=171685


Jan Kusanagi <akarikusanagi at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |akarikusanagi at gmail.com




--- Comment #145 from Jan Kusanagi <akarikusanagi gmail com>  2009-11-13 15:56:29 ---
I have a similar problem, maybe the same, and I found how to reproduce it.
(and have a not-so-nice workaround/fix).

In my case, I get an almost complet keyboard lock, but NumLock and CapsLock do
work.
They turn on/off the LEDs, I mean. I cannot type anything, or use any hotkey.

I was able to reproduce this under Mandriva GNU/Linux with KDE 4.3.2, but also
all prior KDE 4 versions since 4.2.0. Both with kwin desktop effects and
without them.
Also reproduced under Arch GNU/Linux with KDE 4.3.3, without kwin desktop
effects.


How to reproduce:
My setup consists of 2 desktops, and at least 2 windows open in each one.
I have a hotkey for switching desktops (super+tab), but the bug happens also if
I do following procedure using the pager-plasmoid to switch.

Steps to reproduce:
Switch from one desktop to the other, and quickly, switch windows with alt+tab,
then quickly switch desktops again with super+tab or the pager, then alt+tab
again. Pretty soon I hit the lockup condition, and no more typing in any
window. Hotkeys don't work.

My way to recover:
With desktop effects enabled, having the "Present Windows" effect enabled, and
assigned to be activated by placing the mouse in the top-left corner, I
activate it, and keyboard starts working normally again. Hotkeys and
everything.


There's no crash, so no backtrace. Maybe I could try executing kwin (if its
actually kwin's fault) from a console, and see the messages while doing my
procedure...

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the Unassigned-bugs mailing list