Summary: | Modifier-only Meta key shortcut for opening Kickoff breaks a lot | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Nate Graham <nate> |
Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | klausschaukelstuhl, plasma-bugs |
Priority: | VHI | Keywords: | regression |
Version: | 5.19.2 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Nate Graham
2020-06-21 15:39:00 UTC
This is reproducible for me on 5.19 as well as git master, BTW. I was manually adding the wrong string. You actually need to add this: [ModifierOnlyShortcuts] Meta=org.kde.plasmashell,/PlasmaShell,org.kde.PlasmaShell,activateLauncherMenu ...And now it works. Also, removing that whole section now also works. So I can't reproduce the bug anymore. Will re-open if I get a reproducible case that's not based on config file misconfiguration the next time it breaks. I just helped a user troubleshoot this on Plasma 5.19.2. She was experiencing this issue her kwinrc file did not have a [ModifierOnlyShortcuts] entry. The Meta key shortcut did not work to launch Kickoff. It started working after I advised her to add the following to the file: [ModifierOnlyShortcuts] Meta=org.kde.plasmashell,/PlasmaShell,org.kde.PlasmaShell,activateLauncherMenu In options.cpp, this is the value that gets assigned to Meta by default if there is nothing set in the config file. Seems like that's not working, or the code that calls is isn't getting run somehow? Now I'm in a broken state again myself. :( I can debug with instructions. my kwinrc file currently includes the following: [ModifierOnlyShortcuts] Meta=org.kde.plasmashell,/PlasmaShell,org.kde.PlasmaShell,activateLauncherMenu yet it's still not working. Restarting KWin has no effect; it's still broken. After I remove that section and restart KWin, the shortcut starts working again. Re-adding it and restarting KWin yet another time has no further effect and it still works. Something odd is going on here... *** This bug has been marked as a duplicate of bug 391322 *** |