Bug 510343 - When updating the command of a custom shortcut - the change is not applied
Summary: When updating the command of a custom shortcut - the change is not applied
Status: RESOLVED DOWNSTREAM
Alias: None
Product: xdg-desktop-portal-kde
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 6.3.6
Platform: Manjaro Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-10-07 13:24 UTC by pditchev
Modified: 2025-10-07 13:33 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 pditchev 2025-10-07 13:24:43 UTC
SUMMARY
When updating the command of a custom shortcut - the change is not applied

STEPS TO REPRODUCE
1. Add a custom command shortcut with "notify-send Test"
2. Set a shortcut, test it. It works
3. Change the command to "notify-send Test2" (via the edit arrow on the shortcut list-item), click Save. 

OBSERVED RESULT
Upon invocation after the edit the produced notification still says "Test".

EXPECTED RESULT
The edit should be applied so that we send notify "Test2"

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 6.15.11-2-MANJARO
KDE Plasma Version: 6.3.6-1
KDE Frameworks Version: 6.18.0
Qt Version: 6.9.2
Comment 1 Bug Janitor Service 2025-10-07 13:33:43 UTC
Thank you for the bug report!

However Plasma 6.3.6 no longer receives updates or maintenance from KDE; active versions are 6.4 or newer. Please upgrade to an active version as soon as your distribution makes it available to you. Plasma is a fast-moving project, and bugs in one version are often fixed in the next one.

If you need help with Plasma 6.3.6, please contact your distribution, who bears the responsibility of providing help for older releases that are no longer receiving updates from KDE.

If you can reproduce the issue after upgrading to an active version, feel free to re-open this bug report.