https://bugs.kde.org/show_bug.cgi?id=453345
Trent M <twilightinz...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |---
Ever confirmed|1 |0
Status|NEEDSINFO |REPORTED
--- Comment #10 from Trent M <twilightinz...@gmail.com> ---
(In reply to Nate Graham from comment #9)
> Can you confirm that when you run `qdbus org.kde.plasmashell /PlasmaShell
> refreshCurrentShell` or `plasmashell --replace`, Kickoff explicitly loses
> its default Alt+F1 shortcut?
It doesn't seem to *lose* the shortcut, however, the presence of any *default*
shortcut is gone, and doesn't ever come back. To clarify what I mean by that,
in System Settings, the keyboard shortcut for Plasma -> Activate Application
Launcher, there are no checkboxes at all under default shortcuts. The only
shortcut that exists is Alt+F1 explicitly defined as a custom shortcut. So I
guess the *default* shorcut is lost, and doesn't come back. But the *custom*
shortcut is left alone.
> If Kickoff also loses the Alt+F1 shortcut, it would make sense. That part of
> the bug is fixed in Plasma 5.26 at least, which should effectively fix this
> bug for you. Losing the shortcut still isn't ideal though.
I suppose it would "effectively" be the case, but with that same definition, I
"fixed" the bug by setting Meta+Space to run the qdbus command to open the
launcher, which only works if the launcher has an Alt+F1 shortcut. I'd prefer
to just bind the launcher to Meta+Space directly, but no keyboard shortcut at
all--Alt+F1, Meta+Space, or otherwise--works after restarting plasmashell.
Perhaps the "remove shortcut requirement for activating launcher" part of the
fix 391322 might have a positive effect on the reliability of shortcuts other
than the default one?
--
You are receiving this mail because:
You are watching all bug changes.
