Bug 495352

Summary: changes to pre-defined keyboard shortcuts are not persistent
Product: [Applications] kdenlive Reporter: Ed <AtomicCanine>
Component: User Interface & MiscellaneousAssignee: Jean-Baptiste Mardelle <jb>
Status: RESOLVED FIXED    
Severity: normal CC: fritzibaby
Priority: NOR Keywords: triaged
Version First Reported In: 24.05.2   
Target Milestone: ---   
Platform: Mint (Ubuntu based)   
OS: Linux   
Latest Commit: Version Fixed/Implemented In: 24.12
Sentry Crash Report:

Description Ed 2024-10-25 17:26:26 UTC 
SUMMARY
changes to pre-defined keyboard shortcuts are not persistent

STEPS TO REPRODUCE
1. start kdenlive
2. open settings -> configure keyboard shortcuts
3. change a shortcut:I wanted F1 for "extract frame"; it is by default "kdenlive handbook"; change the handbook shortcut to "custom: none", click "ok"
4) for the current session, F1 will be as desired
5) save project and close
6) when project is reopened, there will be two F1 shortcuts

OBSERVED RESULT
After making the shortcut changes and saving/exiting the project, the change of F1 to 'none' will not be honored, resulting in two F1 shortcuts.

EXPECTED RESULT
Any changes made to the keyboard shortcuts should be persistent across project sessions

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma:  Linux Mint 21.3
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version:  1.5

ADDITIONAL INFORMATION
Comment 1 emohr 2024-10-26 13:43:06 UTC 
Mmh. Something is wrong. Kdenlive Windows 24.08.2 -> Handbook -> when I start Kdenlive, Handbook is set to Custom -> change to F1 -> OK -> reopen the dialog -> Handbook is reset to Custom

Click on Default -> F1 is set but the button is not changed to F1.

What could that be?
Comment 2 Ed 2024-12-27 13:38:48 UTC 
It APPEARS that this has been resolved in 24.12.0.  My redefined F1 shortcut no longer conflicts with the standard F1 shortcut.
Comment 3 emohr 2024-12-27 16:48:35 UTC 
Thank you for your feedback. Glad to here it works.

I close this bug. If it still appears in the latest version, please feel free to re-open it and update the affected version number.