Bug 346780

Summary: Custom keyboard shortcuts aren't restored after restarting digikam
Product: [Applications] digikam Reporter: Etienne Casaert <etienne.casaert>
Component: Usability-KeyboardAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: caulier.gilles, metzpinguin
Priority: NOR    
Version: 7.1.0   
Target Milestone: ---   
Platform: Slackware   
OS: Linux   
Latest Commit: Version Fixed In: 8.1.0
Sentry Crash Report:
Attachments: Console output with debug spaces

Description Etienne Casaert 2015-04-27 11:04:41 UTC
After creating a new keyboard shortcut scheme, the sortcuts aren't restored after restarting digikam.
When I am going to the keyboard shortcut screen, the new scheme is well selected but all the keyboard shortcuts are empty !
I have to select again the new scheme to restore the shortcuts (at least, they are not lost).

Reproducible: Always

Steps to Reproduce:
1. Create a new keyboard shortcut scheme with new shortcuts
2. Quit and start digikam again


Actual Results:  
All keyboard shortcuts disappeared.

Expected Results:  
Restore the keyboard shortcuts corresponding to the selected scheme after restarting digikam
Comment 1 caulier.gilles 2015-04-27 11:53:26 UTC
turn on debug space as explained here :

https://www.digikam.org/contrib

... and run digiKam on a console. What did you see ?

Gilles Caulier
Comment 2 Etienne Casaert 2015-04-27 19:55:49 UTC
Created attachment 92292 [details]
Console output with debug spaces

See attached file for console output with debug spaces turned on.
Comment 3 Maik Qualmann 2015-04-28 19:53:34 UTC
I can not reproduce the issue. A new keyboard shortcuts scheme is not empty and properly restored after restarting digiKam. Working the keyboard shortcuts scheme in other KDE applications?

Maik
Comment 4 Etienne Casaert 2015-04-29 19:13:13 UTC
(In reply to Maik Qualmann from comment #3)
> I can not reproduce the issue. A new keyboard shortcuts scheme is not empty
> and properly restored after restarting digiKam. Working the keyboard
> shortcuts scheme in other KDE applications?
> 
> Maik

Yes it works with kmail and gwenview.
Comment 5 caulier.gilles 2015-05-16 14:14:05 UTC
Sound like a dysfunction with your account.

Can you create a new temporary account in your computer and start digiKam. Add new shortcuts, close and restart digiKam.

Problem still reproducible ?

Gilles Caulier
Comment 6 Etienne Casaert 2015-05-16 19:37:51 UTC
Unfortunately the problem is still present with a new account !
Comment 7 caulier.gilles 2016-07-06 16:32:50 UTC
This file still valid using last digiKam 5.0.0 ?

Gilles Caulier
Comment 8 caulier.gilles 2016-07-06 16:32:55 UTC
This file still valid using last digiKam 5.0.0 ?

Gilles Caulier
Comment 9 Etienne Casaert 2016-07-07 05:35:00 UTC
My distro (Slackware) doesn't ships Plasma 5.
Fortunately, I can use a live USB stick with the latest Plasma 5 but I have to compile digikam myself.
So wait few days before I can test this issue...
Comment 10 Etienne Casaert 2016-08-12 08:46:45 UTC
Hello,

I've tested this issue with the latest digikam version (5.1.0) and the custom keyboard shortcuts are restored properly if I select "More actions > Save shortcuts to scheme" in the keyboard shortcut configuration window.  If I don't select this option, the keyboard shortcuts aren't restored as previously described.

I don't know if it is the intended behaviour...
Comment 11 caulier.gilles 2016-08-12 09:22:27 UTC
Well no. It must be saved automatically.

I suspect that something must be forced in KF5 API to have this behavior.

Strangely, this work fine on my computer without to play with this option.

Gilles Caulier
Comment 12 Etienne Casaert 2016-08-13 13:18:11 UTC
The keyboard shortcuts are automatically saved even when I don't select the option "Save shortcuts to scheme".

When I restart digikam, in the keyboard shortcut configuration window, my newly created scheme appears in the combo box but without any shortcut associated.  If I select again my scheme in the combo box then the shortcuts reappears !
Comment 13 caulier.gilles 2016-11-26 10:02:42 UTC
This problem still reproducible using digiKam AppImage bundle 5.4.0 pre release
?

It available at this url :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier
Comment 14 Etienne Casaert 2017-01-13 10:46:04 UTC
This issue is still reproducible with the latest AppImage (digikam-5.4.0-01-x86-64.appimage).
Comment 15 Etienne Casaert 2017-01-26 10:12:12 UTC
I can also reproduce this problem with the KDE neon live user edition for digikam 5.4.0.

May be this can help you to reproduce the problem for debugging...
Comment 16 caulier.gilles 2017-01-26 10:41:19 UTC
Try the Linux universal AppImage bundle 5.5.0 pre version instead system based DK.

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier
Comment 17 Etienne Casaert 2017-01-28 13:05:47 UTC
Same problem with AppImage bundle 5.5.0 pre version on KDE neon live edition.
Comment 18 caulier.gilles 2020-08-02 14:45:33 UTC
digiKam 7.0.0 stable release is now published:

https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/

We need a fresh feedback on this file using this version.

Best regards

Gilles Caulier
Comment 19 Etienne Casaert 2020-09-24 18:52:21 UTC
Hello,

I can confirm the bug with digiKam 7.0.0 and digiKam 7.1.0.

Best regards.
Comment 20 caulier.gilles 2023-04-21 05:55:35 UTC
@Etienne

digiKam 8.0.0 is released. This file still valid ?

Gilles Caulier
Comment 21 caulier.gilles 2023-05-13 13:40:19 UTC
Must be fixed in 8.1.0 with bug 469549