SUMMARY Hello, The combination Alt_L + eacute (azerty shortcut) isn't working, it act as if it was already used for something else, but I couldn't find anything about it, and got advised to file a bug report. STEPS TO REPRODUCE 1. Have a french azerty keyboard layout 2. Use the shortcut Alt_L + é (eacute) which is 2 on a qwerty layout OBSERVED RESULT The shortcut get catch by something and can't be used. EXPECTED RESULT I would expect the shortcut to be recognized. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION setxkbmap -query rules: evdev model: pc105 layout: fr variant: azerty options: terminate:ctrl_alt_bksp xev output of the combination: https://pastebin.com/vYYxYqqK I tried to simulate the shorcut and view the logs via xdotool keydown "Alt_L"; xdotool key "XF86LogGrabInfo"; xdotool keydown "eacute"; xdotool key "XF86LogGrabInfo"; xdotool keyup "eacute" keyup "Alt_L" and got this logs : https://pastebin.com/VKtdM8g0 The interesting part seems to be Information [ 18273.657] (II) Printing all currently active device grabs: Information [ 18273.657] Active grab 0x41533981 (core) on device 'Virtual core keyboard' (3): Information [ 18273.657] client pid 1274 /usr/bin/kglobalaccel5 Information [ 18273.657] at 18273560 (from passive grab) (device frozen, state 6) Information [ 18273.657] core event mask 0x3Information [ 18273.657] passive grab type 2, detail 0xb, activating key 11 Information [ 18273.657] owner-events true, kb 0 ptr 1, confine 0, cursor 0x0Information [ 18273.657] (II) End list of active device grabs I then tried to kill kglobalaccel5 and my key combination was working again, but it seems that another process is calling it to access the global shortcut.
Please note that changing the keyboard layout to english didn't change anything
The issue was with KWin using the shortcut Alt + ~ (which is situated on the same key as eacute), I removed the shortcut and it seems to work fine.
*** This bug has been marked as a duplicate of bug 423305 ***