Bug 428483

Summary: meta/super/win key shortcut for app launcher menu doesn't work if the launcher widget is only on the desktop
Product: [Plasma] kwin Reporter: Gauthier <g.guerin>
Component: generalAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED UNMAINTAINED    
Severity: normal    
Priority: NOR    
Version First Reported In: 5.20.2   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Gauthier 2020-10-30 20:33:18 UTC
SUMMARY
If you drag the app launcher from panel to desktop without doing anything else (and checking the shortcut Alt + F1 is still assigned), the super/meta/win key shortcut stops working. If you put back the launcher on the panel the shortcut works again.

Same if I remove the app launcher from the panel and put a new one on the desktop (and assign a shortcut, say alt + F1) the super/met/win key shortcut doesn't work. When I put back the launcher on the panel it works again, the super/meta/win key shortcut works again right away. 

At all times ~/.config/kwinrc does contain:

[ModifierOnlyShortcuts]
Meta=org.kde.plasmashell,/PlasmaShell,org.kde.PlasmaShell,activateLauncherMenu

I have also tried reloading kwin and rebooting the computer after putting the widget on the desktop just in case.

Seems like "looking for the first widget with the global shortcut" does not work if the only widget is on the desktop.

Btw, the reason I want the widget on the desktop is because my panel is on auto-hide and each time I trigger the shortcut to open the menu, the whole panel pops up, which is a little annoying.

Hopefully this is useful a feedback for improvement.
Comment 1 David Edmundson 2023-09-06 10:38:53 UTC
This bug was reported against an outdated version of KWin. We have made many changes since the. 
If the issue persists in newer versions can you reopen the bug report updating the version number.
Comment 2 Gauthier 2023-09-06 10:45:38 UTC
(In reply to David Edmundson from comment #1)
> This bug was reported against an outdated version of KWin. We have made many
> changes since the. 
> If the issue persists in newer versions can you reopen the bug report
> updating the version number.

Yep it seems to be working fine now :) I only tried on Wayland and not on X11 (and cannot easily switch due to a bug where I loose Firefox windows) but I imagine that's since wayland is the focus right now this bug can be marked as solved. Well done for all those Kwin improvements anyway :)