Bug 415617

Summary: Color management profile path uses previous appimage mount point
Product: [Applications] digikam Reporter: John Dickson <jmdickson>
Component: ColorManagement-ViewsAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: minor CC: caulier.gilles
Priority: NOR    
Version: 7.0.0   
Target Milestone: ---   
Platform: Appimage   
OS: Linux   
Latest Commit: https://invent.kde.org/graphics/digikam/commit/97394d1ed35d09482606b1be3e24658f03d591f1 Version Fixed In: 7.2.0
Sentry Crash Report:

Description John Dickson 2019-12-27 17:33:24 UTC 
SUMMARY
In the [Color Management] section of the digikamrc file, there are two keys that have values that are stored as absolute paths: MonitorProfileFile[$e] and WorkProfileFile[$e]. When running the appimage the absolute path to these files changes with each startup. When color management enabled you have to go to settings and reselect the color space each time digikam is started.

STEPS TO REPRODUCE
1. Start digikam from an appimage.
2. Enable color management and select the working color space.
3. Exit digikam.
4. Restart digikam from the appimage.

OBSERVED RESULT
After restarting, open the color management settings and the working color space is empty. The log will also contain messages like:

Digikam::IccManager::IccManager: Cannot open workspace color profile "/tmp/.mount_digikajdJe2d/usr/share/digikam/profiles/srgb-d65.icm"

Where "/tmp/.mount_digikajdJe2d" is the appimage mount point from the previous run instead of the current run:

ls -d /tmp/.mount_digika*
/tmp/.mount_digikaxfI7N9/


EXPECTED RESULT
The working color space would contain the previously selected value.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Linux Mint 18.3 / KDE Plasma Version 5.8.9
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:  KDE Frameworks 5.61.0
Qt Version: Qt 5.13.1 (built against 5.13.1)

ADDITIONAL INFORMATION
Workarounds:
-Disable color management.
-Copy the desired profile to a persistent location and manually edit the digikamrc file to use that file.
Comment 1 caulier.gilles 2020-01-03 16:35:37 UTC 
It's reproducible with 7.0.0-beta2 daily build ?

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

Gilles Caulier
Comment 2 John Dickson 2020-01-05 00:06:30 UTC 
(In reply to caulier.gilles from comment #1)
> It's reproducible with 7.0.0-beta2 daily build ?
> 
> https://files.kde.org/digikam/
> 
> Gilles Caulier

Yes, the beta2 daily build has the same behavior.

Log contains multiple instances of:
Digikam::IccManager::IccManager: Cannot open workspace color profile "/tmp/.mount_digikaf8SVOB/usr/share/digikam/profiles/srgb-d65.icm"

Which corresponds the config file's stored path (updated from a previous run):
~ $ grep WorkProfileFile .config/digikamrc
WorkProfileFile[$e]=/tmp/.mount_digikaf8SVOB/usr/share/digikam/profiles/srgb-d65.icm

but not the path the appimage is currently mounted on:
~ $ ls -d /tmp/.mount_digik*
/tmp/.mount_digikaaI60Pu/

Of course the file is really over here:
~ $ ls /tmp/.mount_digik*/usr/share/digikam/profiles/srgb-d65.icm
/tmp/.mount_digikaaI60Pu/usr/share/digikam/profiles/srgb-d65.icm

John Dickson
Comment 3 Maik Qualmann 2021-01-01 18:30:20 UTC 
Git commit 97394d1ed35d09482606b1be3e24658f03d591f1 by Maik Qualmann.
Committed on 01/01/2021 at 18:28.
Pushed by mqualmann into branch 'master'.

fix color profile paths
Related: bug 430949
FIXED-IN: 7.2.0

M  +2    -1    NEWS
M  +41   -1    core/libs/dimg/filters/icc/iccsettingscontainer.cpp

https://invent.kde.org/graphics/digikam/commit/97394d1ed35d09482606b1be3e24658f03d591f1