Created attachment 170704 [details] Both default, broken version and fixed version of the `kglobalshortcutsrc` file. SUMMARY In the most recent version of plasma released on Arch Linux (6.1.0-1), the Application Menu won't open when pressing an individual Meta key. My keyboard has two Meta keys - one on the left and one on the right. When pressing both at once, the Application Menu opens properly. STEPS TO REPRODUCE 1. Connect a keyboard with two Meta keys. 2. Reset Global Shortcuts in Plasma's System Settings app 3. Take note that the Application Menu will only open if you press both Meta keys at once OBSERVED RESULT The Application Menu only opens if you press both Meta keys at the same time. EXPECTED RESULT The Application Menu should open when one Meta key is pressed individually. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.9.5-arch1-1 (64-bit) KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION When removing `Meta` from `plasmashell`'s global shortcut list, the Meta key opens the Application Menu properly again. There is a `kglobalshortcutsrc` file with the current defaults and a `kglobalshortcutsrc` file with the aforementioned fix applied in the `.tar.gz` file in the attachments.
Have the same issue here Since my panel is in "auto hide" mode, I can see panel being shown as if menu wants to be shown and then closed again, like if pressing meta key is pressing it twice or something Operating System: Nobara Linux 40 KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1
Can this be reproduced for a newly created user? Is this on x11 or wayland?
I can reproduce on Wayland + Git master. Using a keyboard with only 1 Meta key. After assigning Meta again I could open the Application Launcher. After clicking defaults, it didn't work anymore. After playing with the settings a bit (sorry don't remember what exactly I did) it suddenly worked even when selecting default shortcuts. After rebooting today I can reproduce again.
Settings in Shortcuts->plasmashell->Activate Application Launcher: have no effect for me (neither default shortcuts nor custom) Settings in Right click application Menu -> Configure Application Launcher -> keyboard shortcuts do work.
(In reply to fanzhuyifan from comment #2) > Can this be reproduced for a newly created user? Is this on x11 or wayland? Thanks you so much for coming back at me! I just gave it a quick go and I could reproduce it on X11, too However, on X11 I can see a translucent pane sliding up/appearing and immediately sliding down/disappearing again for about 1 second. I also just gave it a try for a newly created user and I could reproduce the error.
Created attachment 170825 [details] The Pane that is temporarily visible instead of opening up the Application Menu
FWIW I still can't reproduce on git master, wayland with the provided kglobalshortcutsrc. > diff kglobalshortcutsrc.broken kglobalshortcutsrc.fixed > 228c228 > < activate application launcher=Alt+F1\tMeta,Meta\tAlt+F1,Activate Application Launcher > --- > > activate application launcher=Alt+F1,Meta\tAlt+F1,Activate Application Launcher So I changed the line in my kglobalshortcutsrc to > activate application launcher=Alt+F1\tMeta,Meta\tAlt+F1,Activate Application Launcher and both Meta and Alt+F1 work as expected. See also BUG 486246.
FWIW I still cannot reproduce by replacing my kglobalshortcutsrc with the provided kglobalshortcutsrc.broken on wayland, arch linux, plasma 6.1.... So probably some other factor is involved here, not just the kglobalshortcutsrc file.
(In reply to fanzhuyifan from comment #8) > FWIW I still cannot reproduce by replacing my kglobalshortcutsrc with the > provided kglobalshortcutsrc.broken on wayland, arch linux, plasma 6.1.... So > probably some other factor is involved here, not just the kglobalshortcutsrc > file. Because of the error occuring on my PC but not on my laptop, I assumed that it might be for the keyboard having 2 Meta keys. But this does not seem to be the case, then. Is there anything I could try out or analyze?
Unfortunately no one can reproduce it. Are you still experiencing the issue in Plasma 6.2?