kded4 eating keyboard events

Andreas Hartmetz ahartmetz at gmail.com
Thu Sep 25 11:50:09 BST 2008

Am Mittwoch 24 September 2008 01:03:09 schrieb Andreas Pakulat:
> On 23.09.08 23:44:59, Andreas Pakulat wrote:
> > Hi,
> >
> > I'm sorry having to wake up an old thread, but I thought the problem of
> > kded4 locking up the keyboard events was solved. Apparently its not, at
> > least I just hit that problem, that is after closing a konqueror window
> > via Alt+f4 I've ended up with no keyboard response, so I'm believing
> > that kded4 grabbed the keys from X11 and didn't release the keyboard.
> >
> > Is that not fully solved yet or am I the only one seeing this?
> Ok, it wasn't kded4 but kwin that was grabbing the keyboard - except
> Ctrl+Alt+F1. I guess I managed to hit two shortcuts pretty fast after
> another or something else screwed up state in kwin a bit...
> Andreas

When kded4 eats your keyboard it is often a lockup in an unrelated module, the 
last one was in some KDirWatch backend. If it happens log in on the machine 
using ssh and attach gdb to kded4. The piece of code you find yourself in 
then is usually the culprit.

More information about the kde-core-devel mailing list