Bug 421166 - KRunner shortcuts duplicated as "Run Command"
Summary: KRunner shortcuts duplicated as "Run Command"
Status: RESOLVED DUPLICATE of bug 404296
Alias: None
Product: frameworks-kglobalaccel
Classification: Frameworks and Libraries
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-05-07 20:02 UTC by Lastique
Modified: 2020-05-14 22:14 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lastique 2020-05-07 20:02:56 UTC
SUMMARY

In the KDE System Settings, KRunner hotkey shortcuts are duplicated in two categories: "KRunner" and "Run Command". The available actions and default key bindings are the same. However, the key bindings in the "Run Command" category do not work.

STEPS TO REPRODUCE

1. Go to KDE System Settings -> Shortcuts -> Global Shortcuts.
2. In the Components column, see the two categories: "KRunner" and "Run Command".
3. Make sure a hotkey for a given action is bound in the "Run Command" category. For example, make "Run Command" -> "Run Command" is bound to Alt+F2.
4. Press Alt+F2.
5. Change Alt+F2 to be used in "KRunner" -> "KRunner" action (this will unbind it from "Run Command" -> "Run Command").
6. Press Alt+F2 again.

OBSERVED RESULT

The available actions and default hotkeys in "KRunner" and "Run Command" are the same.
At step 4, pressing Alt+F2 doesn't do anything.
At step 6, pressing Alt+F2 does invoke KRunner, as expected.

EXPECTED RESULT

I don't see the reason for this duplication, especially when one of the shortcut categories doesn't work. There should be one place to configure KRunner shortcuts, and the shortcuts configured there should work.

SOFTWARE/OS VERSIONS

Operating System: Kubuntu 20.04
KDE Plasma Version: 5.18.4
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8
Comment 1 Nate Graham 2020-05-14 22:14:34 UTC
Yeah this happened because we renamed the entry. But whenever a shortcut provider's name changes or it's removed, the old entry hangs around. It's safe to remove the old one, but there is no technically feasible way to fix this and do it automatically before the KDE Frameworks 6 timeframe. :(

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