Summary: | evdev driver + khotkeys breaks up arrow - kglobalaccel GlobalShortcutsRegistry::keyPressed: Got unknown key "Up" | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-kglobalaccel | Reporter: | Tomasz Czapiewski <xeros> |
Component: | general | Assignee: | Martin Flöser <mgraesslin> |
Status: | REPORTED --- | ||
Severity: | normal | CC: | fgunni, kdelibs-bugs, sklep, thomas.luebking, xeros |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Tomasz Czapiewski
2010-11-07 01:38:00 UTC
I meant: Up arrow works in console and in X+GL games even when khotkeys are _enabled_. 1) Turn off the PrintScreen key that launches KSnapShot when pressed 2) Log off & log in The problem should dissapear. It is a very dissapointing bug... Thanks Terrible Monster! Indeed it was a problem with PrintScreen shortcut to KSnapShot. After changing shortcut to for example Scroll Lock, up arrow started to work (I haven't even need to logout and login). Yes, it is a dissapointing bug which is here for long time. I wonder if noone else than us was affected by it as there was no bug report for it before I've post it. Exact problem occured to me for about 2 days now. I am on Kubuntu 10.10 and KDE4.6RC though had never problems before. That's a weird bug. Textshells on other VTs are naturally not affected (no evdev etc.) and the "GL games" will likely juts grab the keyboard (and mouse) ie. receive all input exclusively. So that's not significant. It sounds like the keyboard map changes at some point and the key that was originally grabbed as "print" is now the up arrow - but then disabling the hotkeys daemon would make kglobalaccel unselect the key that is *now* "print", so "up" would remain selected and not be usable.... I could assume that the multiseat conditon is relevant - the recognition of one keyboard pollutes the configuration of the other (but that would likely be an evdev bug, to begin with) => Is this still a bug? (It's been quite a while, sorry that nobody looked at it) Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved. |