https://bugs.kde.org/show_bug.cgi?id=484400
Bug ID: 484400
Summary: digikam doesn't find DB anymore after change of
settings
Classification: Applications
Product: digikam
Version: 8.3.0
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: general
Assignee: digikam-bugs-n...@kde.org
Reporter: kde-b...@kristiankoch.com
Target Milestone: ---
SUMMARY
***
After trying to find out more about bug #484398, i stumbled into another one. I
changed two settings:
1. Under Metadata -> Behaviour -> Write Metadata, I checked two additional
boxes, face markings and GPS coordinates (all others were already checked
before).
2. I checked Metadata -> Side Car Files -> compatibility with commercial
programs, but I UNCHECKED again, after the info box appeared
Then, I saved. After this, digikam told me that I selected a new folder for the
database (which was not true) and asked me whether to copy or start over. I
selected copy but it failed. With the other option digikam started completely
fresh. So, I closed it.
The file digikam4.db was gone in my database folder. Fortunately, digikam has
made a copy of the database, so I copied and renamed it to digikam.db. After
restarting, It showed my photos and a welcome message. Since then (roughly 60
minutes ago) digikam is indexing everything again and is now at 25%...
OBSERVED RESULT
See above.
EXPECTED RESULT
Keep database as is.
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: 6.8.1-arch1-1 (64-bit) / 6.0.2
(available in About System)
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
ADDITIONAL INFORMATION
I can only access my backups in a couple of days I try to reproduce completely
because I'm not at home right now.
--
You are receiving this mail because:
You are watching all bug changes.
