Bug#551661: kwin: eats all keystrokes after switch desktop and requesting alt-tab
On Monday 19 October 2009 21:52:35 Yann Dirson wrote:
> Package: kde-window-manager
> Version: 4:4.3.1-1
> Severity: important
>
> Context: this is a machine with several users (in several
> simultaneously-running sessions on the same seat) and "only" 1.5GB of
> RAM, so things get swapped out before one user comes back to the seat
> while others use it.
>
> In my session I have one "main" desktop with light apps, and another
> one which holds a handful of firefox windows. When I switch to this
> FF desktop, it takes some time for it to get responsive - I am not
> sure it is only a matter of FF being swapped out, since even the
> active window frame drawn by kwin does not get drawn before a couple
> of seconds.
>
> Now if I do not wait for the "desktop switch" to "stabilize" after
> Ctrl-F2, and start going Alt-TAB-TAB in the hope to reach a particular
> FF window rapidly, it sometimes happen that the keyboard stops
> responding:
>
> - no wm shortcuts (alt-tab, ctrl-Fn, etc)
> - no key event receieved by the active window
> - still able to switch desktop and apps with the mouse
> - still able to Ctrl-Alt-Fn to another VC and use the keyboard there
>
> Now if I "killall kwin" and switch back to X, I can then use the
> keyboard again and restart one from my xterm, and all is good (until
> the time I get impatient again).
>
> What kind of additional information would be useful here ?
There is a few keyboard-eating bugs in kde, unfortunately. One of them got
afaik fixed in the 4.3.2 release available in unstable.
/Sune
--
How might I do for forwarding to the firewall?
You neither have to debug the secret code, nor should rename a URL over the
server to overclock the memory to a front-end of the window.
Reply to: