Hi all,
On 19/08/2017 13:34, Freddie Witherden wrote:
> I have tried the various maintenance options to no avail. Is there a
> specific means of forcing Digikam to refresh its metadata from whence it
> came, ignoring everything in its own DB?
So I've been having a go at debugging this. Namely, I fired up digikam
with -f -e open to track every open syscall (you can't reread metadata
unless you open up some images). I then ran the Album -> Reread
metadata action. According to the console output one metadata task is
created and one job finishes. However, other than a thread opening some
shared libraries, there are zero other calls to open. This implies that
something may be awry with the reread metadata action.
Regards, Freddie.