https://bugs.kde.org/show_bug.cgi?id=365890
--- Comment #4 from o.ha...@gmail.com ---
Created attachment 142927
--> https://bugs.kde.org/attachment.cgi?id=142927=edit
Patch for KGlobalAccel 5.87.0 that fixes the issue.
Here is what I have found after digging through the code for a while.
The problem lies with KGlobalAccel registering keyboard grabs for every
keycode that could possibly create the desired keysym, regardless of
the state of the Mod5 (Neo Mod3) and Mod3 (Neo Mod4) modifiers.
The function in question is KGlobalAccelImpl::grabKey in
src/runtime/plugins/xcb/kglobalaccel_x11.cpp (KGlobalAccel).
I have written a patch that should fix this issue, but I have only
tested it with Neo, so it might break with other layouts.
The patch is for KGlobalAccel version 5.87.0, but the offending code
is 6 years old by this point so it should work pretty much everywhere.
The fact that global shortcuts are not actually triggered when using the
Neo layers 3 and above, is a separate bug in KWindowSystem, where the
XKeyPressEvent is not translated to the correct keysym and only the first
two columns of the keysym table (Neo layers 1 and 2) are checked.
Anyone interested in fixing this can check out xcbKeyPressEventToQt()
in src/platforms/xcb/kkeyserver.cpp (KWindowSystem).
Furthermore, shortcuts containing dead keys or Unicode characters seemingly
do not even get to the point of registering a keyboard grab, whereas others,
like ÄÖÜ do register a grab, but are still not triggered correctly.
--
You are receiving this mail because:
You are watching all bug changes.
