Bug 485833 - Metadata is ignored while importing in 8.3
Summary: Metadata is ignored while importing in 8.3
Status: REPORTED
Alias: None
Product: digikam
Classification: Applications
Component: Database-Scan (show other bugs)
Version: 8.3.0
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-20 02:56 UTC by ffgg8686
Modified: 2025-04-11 18:13 UTC (History)
2 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description ffgg8686 2024-04-20 02:56:48 UTC 
SUMMARY
Metadata is ignored while importing in 8.3, and I have to manually "Re-Read Metadata" command to get Digikam 8.3 to read metadata from file. This behaviour wasn't present in 8.2 version I used before.

STEPS TO REPRODUCE
1. Import image with known metadata into Digikam 8.3
2. Click on newly imported images with metadata
3. Observe the issue 

OBSERVED RESULT
Metadata is not imported automatically, leaving all Metadata and Captions field empty.

EXPECTED RESULT
Metadata and Captions section is automatically populated upon importing images

SOFTWARE/OS VERSIONS
Digikam8.3 / Windows: 10

ADDITIONAL INFORMATION
Comment 1 Maik Qualmann 2024-04-20 06:01:29 UTC 
The problem is fixed in digiKam-8.4.0. Under stress on the SQLite database, records could be lost. Please test the pre-release version of digiKam-8.4.0 from here:

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

Maik
Comment 2 ffgg8686 2024-04-20 06:30:25 UTC 
(In reply to Maik Qualmann from comment #1)
> The problem is fixed in digiKam-8.4.0. Under stress on the SQLite database,
> records could be lost. Please test the pre-release version of digiKam-8.4.0
> from here:
> 
> https://files.kde.org/digikam/
> 
> Maik

Hi, what do you mean by "Under stress on the SQLite database, records could be lost."? Does this mean database could be resetted, and start from a blank?
Comment 3 Maik Qualmann 2024-04-20 06:38:50 UTC 
The problem of a locked database when multiple processes accessed the DB at the same time has existed in digiKam for a long time. However, during a certain database operation, the database was completely locked and the data record was lost. We have been aware of the problem that not all metadata was captured during import for a long time and have a long list of bug reports about it. This should now be fixed with digiKam-8.4.0. You don't need to start with a new database, you may just have to re-read the metadata if you find affected images.

Maik
Comment 4 caulier.gilles 2024-04-20 07:17:41 UTC 
8.4.0 pre-release bundle can be tested. Windows installer is here :

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

Gilles Caulier
Comment 5 caulier.gilles 2025-04-11 18:13:53 UTC 
Hi,

The 8.7.0 pre-release Windows installer from today have been rebuilt from
scratch with Qt 6.8.3, KDE 6.12, OpenCV 4.11 + CUDA support, Exiv2 0.28.5, ExifTool 13.27, ffmpeg 7, all image codecs updated to last version (jxl, avif, heif, aom, etc.).

Please try with this version to see if your problem still reproducible...

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

Thanks in advance
Best regards

Gilles Caulier