Bug 492179 - keyboard shortcuts for "commands" cannot be successfully edited in system settings -> keyboards -> shortcuts menu
Summary: keyboard shortcuts for "commands" cannot be successfully edited in system set...
Status: RESOLVED WORKSFORME
Alias: None
Product: systemsettings
Classification: Applications
Component: general (show other bugs)
Version: 6.1.4
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-08-25 20:29 UTC by Liz Lee
Modified: 2024-08-26 11:19 UTC (History)
0 users

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


Attachments
before change (1) (53.63 KB, image/jpeg)
2024-08-25 20:29 UTC, Liz Lee
Details
changing entry (2) (56.29 KB, image/jpeg)
2024-08-25 20:29 UTC, Liz Lee
Details
after changing entry (3) (51.35 KB, image/jpeg)
2024-08-25 20:30 UTC, Liz Lee
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Liz Lee 2024-08-25 20:29:27 UTC
Created attachment 172945 [details]
before change (1)

STEPS TO REPRODUCE
1. "+ add new" "command or script" in the "system settings" -> "keyboard" -> "shortcuts" menu.
2. try to change the shortcut via the "edit command for [...]" button save it.

OBSERVED RESULT
changes are only shown in the entry in the left column. they are not actually changed though. shortcut does still work as assigned before the change, the new change is ignored.

EXPECTED RESULT
shortcut for command should be changed.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 40
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2
Kernel Version: 6.10.6-200.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Comment 1 Liz Lee 2024-08-25 20:29:51 UTC
Created attachment 172946 [details]
changing entry (2)
Comment 2 Liz Lee 2024-08-25 20:30:09 UTC
Created attachment 172947 [details]
after changing entry (3)
Comment 3 Liz Lee 2024-08-26 11:19:59 UTC
ok, turns out it does work after a re-login/reboot.

i think kde plasma should be more actively communicate the need for re-logins in certain circumstances. the average user expects something to work after clicking "apply". when an action needs a re-login to take effect this should be communicated to the average user, otherwise this might lead to the average user being frustrated _very_ quick.