You are not logged in.
kglobalaccel5 might grab the "wrong" key (resolving the symbol to the code for the qwert* layout and then misapplying it to the koy one)
1. kill kglobalaccel5
2. run xev again to record the actually significant event (codes produced and everything else), also test the shortcut now to see whether it acts as expected
3. re-start kglobalaccel5 while the koy layout is active and re-try the behavior
This happens with kglobalaccel5 turned off (key works as expected):
KeyPress event, serial 40, synthetic NO, window 0x600001,
root 0x7a2, subw 0x0, time 155032, (-687,188), root:(184,659),
state 0x0, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 40, synthetic NO, window 0x600001,
root 0x7a2, subw 0x0, time 155368, (-687,188), root:(184,659),
state 0x4, keycode 52 (keysym 0x78, x), same_screen YES,
XLookupString gives 1 bytes: (18) "▒"
XmbLookupString gives 1 bytes: (18) "▒"
XFilterEvent returns: False
KeyRelease event, serial 40, synthetic NO, window 0x600001,
root 0x7a2, subw 0x0, time 155496, (-687,188), root:(184,659),
state 0x4, keycode 52 (keysym 0x78, x), same_screen YES,
XLookupString gives 1 bytes: (18) "▒"
XFilterEvent returns: False
KeyRelease event, serial 40, synthetic NO, window 0x600001,
root 0x7a2, subw 0x0, time 155768, (-687,188), root:(184,659),
state 0x4, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: FalseWith kglobalaccel5 on:
KeyPress event, serial 40, synthetic NO, window 0x8000001,
root 0x7a2, subw 0x0, time 365912, (-347,298), root:(524,769),
state 0x0, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
FocusOut event, serial 40, synthetic NO, window 0x8000001,
mode NotifyGrab, detail NotifyAncestor
FocusIn event, serial 40, synthetic NO, window 0x8000001,
mode NotifyUngrab, detail NotifyAncestor
KeymapNotify event, serial 40, synthetic NO, window 0x0,
keys: 1 0 0 0 32 0 16 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
KeyRelease event, serial 40, synthetic NO, window 0x8000001,
root 0x7a2, subw 0x0, time 366216, (-347,298), root:(524,769),
state 0x4, keycode 52 (keysym 0x78, x), same_screen YES,
XLookupString gives 1 bytes: (18) "▒"
XFilterEvent returns: False
KeyRelease event, serial 40, synthetic NO, window 0x8000001,
root 0x7a2, subw 0x0, time 366360, (-347,298), root:(524,769),
state 0x4, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: FalseThis looks the same except of the grab. But I don't see any keybind for Ctrl+x anywhere tbh
Last edited by Stormf0x (2023-12-15 11:12:39)
Offline
I "solved" the issue now, by switching to a wayland session, that works flawlessly. This might actually by a bug in kde, but I don't have the time to further investigate this, tbh.
Offline
This here is still bonkers
state 0x4, keycode 52 (keysym 0x78, x), same_screen YES,
XLookupString gives 1 bytes: (18) "▒"
XmbLookupString gives 1 bytes: (18) "▒"XmbLookupString is particularily interesting because it's part of XIM, if you're curious (or just willing to scratch my itch) compare "printenv" in the X11 and wayland session (though the latter is probably not really comparable anyway wrt IM, so just post printenv for the X11 session)
https://wiki.archlinux.org/title/Input_method
Offline