Bug 451821

Summary: Hotkeys don't work unless the keyboard languages are arranged in a specific order
Product: [Frameworks and Libraries] frameworks-kglobalaccel Reporter: starw1nd
Component: generalAssignee: kdelibs bugs <kdelibs-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: butirsky, kde, nate
Priority: NOR    
Version: 5.92.0   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description starw1nd 2022-03-23 11:33:09 UTC 
SUMMARY

Some hotkeys, especially those utilizing the Meta key (Meta+E, Meta+D), and the Ctrl-Alt-T shortcut to launch default terminal don't work on a system with 3 keyboard languages: Russian, Ukrainian and English (German, Swedish and Finnish variant, though the same thing happens with the default US layout), even when English is the active layout. When they're arranged so that anything but English is at the first place (so, for example, 1. Russian 2. Ukrainian 3. English, or 1. Ukrainian 2. English 3. Russian etc), the specified shortcuts don't work. With English at the very top, however, everything works as expected

STEPS TO REPRODUCE
1. Add Russian and Ukrainian layouts to the keyboard layout list, make the English layout be anywhere but the first place
2. Try using Meta+E, Meta+D, Ctrl-Shift-T 

OBSERVED RESULT

Shortcuts don't work unless I go back to settings and make English the topmost language

EXPECTED RESULT

Shortcuts work despite the position of the English layout

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.24.3
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION

Kernel 5.16.16-arch1-1
X11
EndeavourOS
Comment 1 Nate Graham 2022-03-26 23:05:29 UTC 
Cannot reproduce on Wayland; when I add Russian and Ukrainian keyboard layouts, and move English to the past position, those Meta shortcuts work fine for me.

Does it work on Wayland for you? Or is it broken there too?
Comment 2 Andrey 2022-03-28 11:27:13 UTC 
Seems like old X11-specific (it probably not even Plasma one)

*** This bug has been marked as a duplicate of bug 309193 ***