Version: (using KDE 4.3.1) OS: Linux Installed from: Gentoo Packages Regression, this worked well with KDE 4.2.4. Description: The special application/window option to block global shortcuts gets ignored when triggering a combined shortcut (e.g. STRG + F1) and using different keyboards for each keystroke. If each key of the shortcut is pressed on the same keyboard, the option works as expected, the global KDE Shortcut to switch to Desktop 1 gets ignored and the action of the applicaton wich is associated with this key combination is triggered. However pressing each key on a different keyboard the option gets ignored and the global KDE shortcut is triggerd. Steps to reproduce: 1. Set the option to block global shortcuts for an application (e.g xev) and make sure the application has the focus. 2. press STRG on keyboard 1 3. press F1 on keyboard 2 4. release F1 on keyboard 2 5. press F1 on keyboard 2 again 6. release F1 on keyboard 2 7. release STRG on keyboard 1 Sometimes F1 has to be pressed only once. Application Information: kernel: 2.6.31 xorg-server: 1.6.3 evdev: 2.1.3
Created attachment 36814 [details] lshal output
Created attachment 36815 [details] xev output within KDE 4.3.1 xev output when following the reproducing steps within KDE 4.3.1
Created attachment 36816 [details] xev output within x11 failsave
oops i ment CTRL instead of STRG
ok i got a bit of time to dig into this and as far as it seems in the package ' kdebase/runtime/kglobalaccel' the method 'KGlobalAccelImpl::x11MappingNotify' calls the Method 'GlobalShortcutsRegistry::grabKeys()' which activates all global hotkeys ignoring the "block global shortcuts" settings. So whenever the xserver casts an mappingnotify event all global hotkeys gets activated. With the patch below the behaviour as of 4.2.4 is restored. The patch isn't a real fix it just makes KDE useable for me again.
Created attachment 37775 [details] patch wich restores the 4.2.4 behaviour
Sorry for the delay. Is this still an issue? --- KGlobalAccel needs it's own bugzilla component ;-)
"Yes, is" - and as comment #5 figured, it's a problem with kglobalaccel, kwin is not involved. Actually double press/releasing a global shortcut key on a secondary keyboard breaks global shortcut deactivation - 1st one is caught, second passes Afterwards the "primary" keyboard (the one that had interacted on the window before) isn't blocked anymore either.
Reassigning to kglobalaccel