Bug 347031

Summary: Cannot change custom shortcut action under certain circumstances
Product: [Unmaintained] khotkeys Reporter: Enno Köster <ennokoester>
Component: generalAssignee: Michael Jansen <kde>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version: 5.3.0   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Enno Köster 2015-05-02 00:12:49 UTC
When you change the command of an existing custom shortcut, hit apply and leave the configuration page, then it does not save the changed command.
When you do exactly the same, hit apply, then create a new shortcut and hit apply again, then it _does_ save the changed command of the existing shortcut.
Deleting a different existing shortcut instead of creating one also helps.

Reproducible: Always

Steps to Reproduce:
1. Create custom shortcut for a command ("notify-send foo bar" for example)
2. Close and Reopen the custom shortcut KCM and navigate to the shortcut you created
3. Change the command of the shortcut to something else and hit apply
4. Repeat step 2

Actual Results:  
The command of the shortcut is still the one that you entered in step 1

Expected Results:  
It should be the new command you entered in step 3

If you create a shortcut, then change the command of another existing shortcut and then leave and reenter the custom shortcut KCM, it results in the newly created shortcut and the change to the existing shortcut getting lost.

So basically it seems like all changes done get lost every time the last action was an edit rather then an add or delete.
Comment 1 Enno Köster 2015-05-10 11:34:04 UTC
Update:
I tried the same on my laptop and it worked without problems so there is something special to the configuration on my PC.
Any hint in which direction I should continue my search would be greatly appreciated.

PS: i installed arch on  both computers a few months from each other so differences in the packages are unlikely. both were installed with kde4 and later moved to plasma 5.2.
I did less configuring on my laptop which i do not use as much currently so my guess is that I somehow broke things on my PC. i'd like to find out how so it can be avoided in the future.
Comment 2 Thomas Lübking 2015-10-10 21:52:52 UTC

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