https://bugs.kde.org/show_bug.cgi?id=401767
Bug ID: 401767
Summary: digikam unable to find existing path
Product: digikam
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Database
Assignee: digikam-bugs-n...@kde.org
Reporter: ka...@seznam.cz
Target Milestone: ---
After shuffling around disks, Digikam complains about unability to find a
collection in existing (!!!) path.
STEPS TO REPRODUCE
1. have /home/youruser/yourphotos set in digikam
2. change the uuid of the device where the directory resides (e.g. tune2fs -U
... for ext4fs)
3. start Digikam
OBSERVED RESULT
it reports error on start:
Collection not found - digiKam
The collection
(Folder '/home/youruser/yourphotos' on the volume with the id "...")
is currently not found on your system.
Please choose the most appropriate option to handle this situation:
[ ] The collection is located on a storage device which is not always attached.
Mark the collection as a removable collection.
[o] Take no action now. I would like to solve the problem later using the setup
dialog
EXPECTED RESULT
No such nonsense, digikam should not rely on the underlaying layout of disks.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.9.0
(available in About System)
KDE Plasma Version: 5.14.3
KDE Frameworks Version: 5.52.0
Qt Version: 5.11.1
ADDITIONAL INFORMATION
Going to settings => Database => Database Settings => browsing for the path and
confirming /home/youruser/yourphotos again doesn't help
Going to settings => Collections => Local Collections, I can only edit the name
"Col. 0" but I see no path settings
Note, this might be duplicate of bug 215486 but that deals with system upgrade.
This isn't the case, this is solely about nonsensical insisting on UUID match.
--
You are receiving this mail because:
You are watching all bug changes.
