Bug 479758 - Loss metadata from items.
Summary: Loss metadata from items.
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Maintenance-Metadata (show other bugs)
Version: 8.3.0
Platform: Microsoft Windows Microsoft Windows
: NOR major
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-01-13 18:53 UTC by jm7@acm.org
Modified: 2024-01-13 19:19 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 8.3.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jm7@acm.org 2024-01-13 18:53:41 UTC
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Unfortunately, I am a bit unclear on how this has happened.  But it may have to do with modifying metadata for  large numbers of images at once.  
2. 
3. 

OBSERVED RESULT  
Loss of ALL Metadata tags and GPS information and faces.  I lost all this for 15249 files recently.  (Months worth of work).


EXPECTED RESULT
Loss of data should never occur without explicit direction from the user. 

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

ADDITIONAL INFORMATION
Build date: 1/3/2024 11:20 AM (target: RelWithDebInfo)
Revision: 875822f3e66771ed9cb94bb0cf800b6374c4d0f1
Branch: master
Comment 1 Maik Qualmann 2024-01-13 18:58:51 UTC
Do you write the metadata generally into the images or only into the database. Do they use sidecars? What type of database are you using?

Maik
Comment 2 Maik Qualmann 2024-01-13 19:16:09 UTC
Update your digiKam version immediately, you are using a version in which we did an Exiv2 file path test.
You should not use current developer versions without a backup, in principle errors have actually been fixed. But often we just test things, if they catch such a version, such problems can arise. I therefore recommend asking on the developer mailing list whether version XYZ is currently recommended on https://files.kde.org/digikam/.

Maik