SUMMARY When I upgraded to Plasma 5.24.0 it stopped recognising Alt+F1 as the Meta key. For example, if I want to open the application launcher I have to press Alt+F1 now instead of pressing the Meta key. STEPS TO REPRODUCE 1. Open the application launcher settings. 2. Set the shortcut to Alt+F1. 3. Try to use the Meta key. OBSERVED RESULT Nothing happens. EXPECTED RESULT The application launcher opens. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.16.8-arch1-1 (available in About System) KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2
Can you attach your .config/kwinrc file to the bug report please?
Created attachment 146804 [details] kwinrc
(In reply to Vlad Zahorodnii from comment #1) > Can you attach your .config/kwinrc file to the bug report please? I attached it now!
> [ModifierOnlyShortcuts] > Meta=org.kde.kglobalaccel,/component/kwin,,invokeShortcut,Overview This says that you or something else set up your Meta key to open the Overview effect instead of the Application Launcher applet. If you delete those two lines and reboot, Meta should activate the Application Launcher again.
(In reply to Nate Graham from comment #4) > > [ModifierOnlyShortcuts] > > Meta=org.kde.kglobalaccel,/component/kwin,,invokeShortcut,Overview > This says that you or something else set up your Meta key to open the > Overview effect instead of the Application Launcher applet. > > If you delete those two lines and reboot, Meta should activate the > Application Launcher again. Thanks, I tried removing those lines and rebooting, but it still doesn't work.
Does your Application Launcher applet have its shortcut set to Alt+F1? You can check by going to its settings window and then the "Keyboard Shortcuts" page
(In reply to Nate Graham from comment #6) > Does your Application Launcher applet have its shortcut set to Alt+F1? You > can check by going to its settings window and then the "Keyboard Shortcuts" > page Yes, as I mentioned this in the "steps to reproduce" section, the shortcut is set to Alt+F1.
In that case, this is the same thing reported in Bug 391322; marking as a duplicate. *** This bug has been marked as a duplicate of bug 391322 ***