Bug 402346 - The digikamrc file is not recorded into the digikam directory
Summary: The digikamrc file is not recorded into the digikam directory
Status: REOPENED
Alias: None
Product: digikam
Classification: Applications
Component: Setup-Misc (show other bugs)
Version: 7.0.0
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
: 413489 452454 (view as bug list)
Depends on:
Blocks:
 
Reported: 2018-12-19 13:33 UTC by Loukournan29
Modified: 2023-10-15 12:37 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Loukournan29 2018-12-19 13:33:02 UTC
SUMMARY
The digikamrc file is not recorded into the digikam directory

STEPS TO REPRODUCE
1. Install fresh digikam
2. Launch digikam, then quit.
3. 

OBSERVED RESULT
The digikamrc file is recorded into the %localappdata% directory.

EXPECTED RESULT
The digikamrc file should be recorded into the %localappdata%/digikam directory.

SOFTWARE/OS VERSIONS
Windows: 7
MacOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Loukournan29 2018-12-19 13:35:34 UTC
Please provide the resource moving at the upgrade to fixed version.
Comment 2 Maik Qualmann 2018-12-19 17:50:33 UTC
This also applies to other ported programs, e.g. Krita. A system component sets this path.

Maik

*** This bug has been marked as a duplicate of bug 382358 ***
Comment 3 Thomas Debesse 2018-12-19 23:15:12 UTC
Note that the right path to store this file must not be %LOCALAPPDATA%/digikam but must be %APPDATA%/digikam

In fact, KDE inherits a Qt bug: %LOCALAPPDATA% is a directory that is local to a machine, it's meant for local cache and is disposable. %APPDATA% is the user directory that is kept whatever the machine it uses.

In a network-based environment, where the user is working on a network domain, %APPDATA% roams across the machines, %LOCALAPPDATA% not. %LOCALAPPDATA% must not be used for configuration since the user can't read the configuration when he connects from another computer or replace its computer (or if an hardware failure occurs).
Comment 4 Thomas Debesse 2018-12-19 23:20:02 UTC
This is not a duplicate of Bug 382358.

This bug is reporting that digikamrc file must be stored as:
<something>/digikam/digikamrc
instead of:
<something>/digkamrc

Bug 382358 is reporting that <something> must be:
%APPDATA%
instead of:
%LOCALAPPDATA%
Comment 5 Maik Qualmann 2019-10-26 19:58:56 UTC
*** Bug 413489 has been marked as a duplicate of this bug. ***
Comment 6 caulier.gilles 2020-01-12 16:59:55 UTC
We have updated whole Qt to last 5.14 and KF5 to 5.65. Both are responsible of
application settings management.

Can you reproduce the problem with digiKam 7.0.0-beta2 pre release ?

https://files.kde.org/digikam/

Thanks in advance

Gilles Caulier
Comment 7 Loukournan29 2020-01-14 11:03:09 UTC
(In reply to caulier.gilles from comment #6)
> We have updated whole Qt to last 5.14 and KF5 to 5.65. Both are responsible
> of
> application settings management.
> 
> Can you reproduce the problem with digiKam 7.0.0-beta2 pre release ?
> 
> https://files.kde.org/digikam/
> 
> Thanks in advance
> 
> Gilles Caulier

With the 7.0.0-beta2 pre release the digikamrc file is still stored in the %APPLOCALDATA% directory.
Comment 8 Loukournan29 2020-01-15 20:21:11 UTC
(In reply to Loukournan29 from comment #7)

I want to precise that the %APPLOCALDATA%/digikam directory is created by the installation, but the digikamrc file is not stored in.
Comment 9 caulier.gilles 2020-01-16 08:23:28 UTC
This is not a digiKam bug.

As Maik said, Krita has also the dysfunction. Probably other KDE application ported to Windows has the same problem.

As i already said, the common software component used by all KDE application is KF5::KxmlGui. This components as the rules to store configuration files at the  place on operating system. There is no code like this in DK.

Even if this bug is not really a dupplicates of bug #382358, this revelate a problem outside digiKam. It's clear...

Gilles Caulier
Comment 10 chasa.imago 2020-07-30 09:12:39 UTC
https://bugs.kde.org/show_bug.cgi?id=413489

Just adding this info. Did a fresh installation of digikam 7.0.0.
And the location of the digikamrc file is still there, where it always was, in the 'wrong' location. ☻

! C:\Users\[user name]\Appdata\Local !
And not in something like:

C:\Users\[user name]\AppData\Local\digikam
or 
C:\Users\[user name]\AppData\Roaming\digikam



OBSERVED RESULT
wrong location

EXPECTED RESULT
To reside in the logical and expected directory.

SOFTWARE/OS VERSIONS
Windows: Microsoft Windows [Version 10 Pro 2004 19041.388]
Comment 11 Maik Qualmann 2022-04-10 08:47:17 UTC
*** Bug 452454 has been marked as a duplicate of this bug. ***
Comment 12 caulier.gilles 2023-10-15 12:37:54 UTC
@Loukournan29,


This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:

https://files.kde.org/digikam/

This new bundle is based on last Qt framework 5.15.11 and KDE framework 5.110.

Thanks in advance

Gilles Caulier