Bug 442614

Summary: Application Launcher shortcut broken
Product: [Plasma] plasmashell Reporter: matthias.schrumpf
Component: generalAssignee: David Edmundson <kde>
Status: RESOLVED DUPLICATE    
Severity: major CC: nate, plasma-bugs
Priority: NOR    
Version: 5.22.4   
Target Milestone: 1.0   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description matthias.schrumpf 2021-09-17 19:40:27 UTC
SUMMARY
After update 5.22.5, the Application Launcher/Application Menu cannot be opened by pressing the Meta key anymore

STEPS TO REPRODUCE
1. Update to Plasma version 5.22.5
2. Have a button for the application launcher (Kickoff) or application menu (kicker) on your taskbar
3. Hit the Meta key (aka Windows key, the one between Ctrl and Alt on most keyboards). 

OBSERVED RESULT
Nothing happens. 

EXPECTED RESULT
The application menu or launcher should open upon pressing the Meta key. 

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: 
(available in About System)
Operating System: Arch Linux
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2
Kernel Version: 5.14.5-arch1-1 (64-bit)
Graphics Platform: X11

ADDITIONAL INFORMATION
No changes have been made to the default key mapping. Reverting key mapping to defaults did not solve the problem. 
I also tried right-clicking the launcher/menu shortcut and opening its settings to manually change the keyboard shortcut. However, the dialog refuses to accept plain Meta as a keyboard shortcut. It expects a combination of two or more keys. 

(Sorry for opening this issue for version 5.22.4 instead of 5.22.5; that option is not available in the dialog)
Comment 1 matthias.schrumpf 2021-09-20 08:22:03 UTC
Additional information: 
I set a keyboard shortcut (Meta+<) for the application menu. Now it can also be opened by pressing Meta. Both the combination and the plain Meta key will open the menu. When I clear the keyboard shortcut, neither command will work.
Comment 2 Nate Graham 2021-09-21 21:50:13 UTC

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