Bug 488783 - Re-Bind Meta key to KRunner
Summary: Re-Bind Meta key to KRunner
Status: RESOLVED DUPLICATE of bug 371560
Alias: None
Product: kwin
Classification: Plasma
Component: input (other bugs)
Version First Reported In: 6.1.0
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-20 11:30 UTC by Marco G
Modified: 2024-06-20 15:03 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marco G 2024-06-20 11:30:31 UTC
SUMMARY

Since KDE 4 I used to rebind the META key to launch Krunner. This worked also fine in Plasma 6.0.5 but since todays fedora update to 6.1 this is not working anymore.

STEPS TO REPRODUCE
1.  Tried to reeanable with:
`kwriteconfig6 --file ~/.config/kwinrc --group ModifierOnlyShortcuts --key Meta "org.kde.kglobalaccel,/component/org_kde_krunner_desktop,invokeShortcut,_launch"`
2. restart

OBSERVED RESULT
Meta Key now doesnt do anything at all. Not even opening the Start Menu nor Krunner 

EXPECTED RESULT
Krunner opens on META key 

The ~/.config/kwinrc says:
[ModifierOnlyShortcuts]
Meta=org.kde.kglobalaccel,/component/org_kde_krunner_desktop,invokeShortcut,_launch


If I run it manually:
`qdbus org.kde.kglobalaccel /component/org_kde_krunner_desktop invokeShortcut _launch`
it works and krunner opens as expected. But no chance to bind it to just meta.



SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Ultramarine Linux lostumbrella 40 (KDE Plasma Edition) x86_64
KDE Plasma Version: 6.1.0
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.1

ADDITIONAL INFORMATION
Kernel: 6.9.4-200.fc40.x86_64 (64-bit)
Wayland on Mesa
kwin 6.1.0
Comment 1 Nines 2024-06-20 14:24:25 UTC
6.1 introduced proper support for modifier-only shortcuts. Can you try removing that fragment from kwinrc and setting the shortcut using the system settings? It works brilliantly here.
Comment 2 Nines 2024-06-20 15:03:07 UTC

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