https://bugs.kde.org/show_bug.cgi?id=384603
--- Comment #13 from digi...@homemp3.dyndns.org --- Even simpler: I found out that simply touching the file (updating the last modified timestamp in the file system, using the "touch" command) and then re-reading the metadata from file gives the file its Camera Creation Time (which is then correctly taken from the EXIF tag, not the file timestamp). This seems to imply that Digikam is keeping state about whether a file has changed since last read, and the "re-read ..." command seems a no-op if the file modification time is at or before the time when Digikam thinks it read the file last. I would expect an explicit "re-read..." operation to re-read, no matter what the time stamps say. Above and beyond that, of course, the root cause for the missing Camera Creation Date needs to be found, particularly after Mike suggested that an empty Camera Creation Date cannot occur at all (although it does here). -- You are receiving this mail because: You are watching all bug changes.
