Currently at version 5.1, but this bug goes back to the 4s. About 20% of the time sidecar metadata doesn't get loaded correctly. There are two situations: 1) initial scan I'm moving images into digikam. About 20% of the time the whole directory will not be scanned. Perhaps something is crashing silently or perhaps the database is busy. Tags don't come up, versions don't come up, but the metadata tag shows the tags and imagehistory. A reread metadata usually fixes it, but on to 2. 2) reread About 20% of the time on a reread the image metadata doesn't get incorporated. Images will have information in the metadata tab, but labels and versions don't show up. This is mostly noticeable when selecting a bunch of files from a directory that wasn't loaded on the initial scan. Select all files and reread results in a Swiss cheese of files that have metadata incorporated. Rereading multiple times often doesn't even fix it(and also can take a very long time, because it seems to reload the thumbnails). It's like 20% don't incorporate, but the same 20%. So I have to go in by hand and reload the broken ones one at a time, which works.
Can you reproduce the problem using digiKam Linux AppImage bundle ? The last bundle is available at this url: https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM Gilles Caulier
Git commit e6e76cf0cf8b34f028511958070f98f457eef81a by Maik Qualmann. Committed on 15/09/2019 at 06:47. Pushed by mqualmann into branch 'master'. less locked database during the initial scan Related: bug 389949, bug 411927 FIXED-IN: 6.4.0 M +3 -1 NEWS M +8 -4 core/libs/database/collection/collectionscanner_scan.cpp https://invent.kde.org/kde/digikam/commit/e6e76cf0cf8b34f028511958070f98f457eef81a