"Date taken" corruption on metadata change, especially captions

Maik Qualmann metzpinguin at gmail.com
Thu Oct 24 06:57:40 BST 2024


Unfortunately, there is a bug in digiKam-8.4.0 that means that the entries for 
rating, creation date and digitization date are not read correctly when images 
are imported for the first time.
So you have to read the metadata from the file again for all images imported 
with digiKam-8.4.0. This corrects the first incorrect metadata import.

Maik

Am Donnerstag, 24. Oktober 2024, 01:39:26 Mitteleuropäische Sommerzeit schrieb 
Charlie Gorichanaz:
> Hello,
> 
> I've recently found Digikam seems to be corrupting the dates on my photos.
> I believe this happened after I ran an update from Arch Linux package
> digikam-8.4.0-1 to digikam-8.4.0-2, which was built September 21 and which
> I installed more recently than that.
> 
> I am in Pacific time and my Linux computer is configured as such, in UTC-7.
> My photos are a combination of files from a Pixel phone (with filenames
> using the UTC timestamp) and Nikon Z7ii. I haven't figured out exactly what
> is happening, but I noticed the files jump around in my album after I add
> flags or write captions. This can happen multiple times. It seems like they
> jump ahead by 7 or 14 hours upon such metadata changes. If I edit a single
> photo's caption multiple times, the file can end up several days after
> where it should be in the album. This is driving me crazy, as I am trying
> to sort photos chronologically for the purpose of writing journals and
> blogs.
> 
> For example, here's a photo I edited the caption about 10 or 15 times. You
> can see the "camera created date" showing below the thumbnail is 09-05
> 06:33 despite that it should be 08-29 20:33 local time or 08-30 03:33 UTC.
> I see now none of the metadata fields with "date" in the name actually have
> that 09-05 date, so I'm not sure where it's coming from.
> 
> [image: screenshot_2024-10-23_163148.png]
> 
> Is anyone else experiencing something like this?
> 
> Note I am unfortunately not 100% sure if this was working correctly for me
> on Arch 8.4.0-1. The fact that package exists on my local system makes me
> think I was using 8.4.0 successfully before I installed the 8.4.0-2 package
> recently, but the changes
> <https://gitlab.archlinux.org/archlinux/packaging/packages/digikam/-/commit/
> b9a9eee00bd55376cac33070d3632e93d61ad443> there seem so small I am not sure
> what the problem could be. So there's a chance I was using 8.3.0 when this
> was working.
> 
> Thank you,
> Charlie Gorichanaz
> 
> P.S. I will be on a short camping trip for the next few days, so I may not
> be able to reply promptly, but I will certainly be back! Thanks.






More information about the Digikam-users mailing list