Bug 426857

Summary:	Creation date/time not show correctly
Product:	[Applications] digikam	Reporter:	Tom de Geus <tom>
Component:	Metadata-Exif	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	caulier.gilles, metzpinguin
Priority:	NOR
Version:	7.1.0
Target Milestone:	---
Platform:	macOS (DMG)
OS:	macOS
Latest Commit:		Version Fixed In:	8.1.0
Sentry Crash Report:
Attachments:	Screenshot with observed behaviour Problematic photo

Description Tom de Geus 2020-09-22 09:24:20 UTC

Created attachment 131861 [details]
Screenshot with observed behaviour

SUMMARY

Date/time of photo not shown correctly (the shown time is even before the photo was taken)


STEPS TO REPRODUCE

I'm trying to sort based on date/time that the photos were taken. However, I get a strange result as shown in the screenshot.


OBSERVED RESULT

The shown date is 13.07.19 06:53


EXPECTED RESULT

The exif information reveals 2019:07:13 12:53:34


SOFTWARE/OS VERSIONS
Windows: 
macOS: x
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

See https://invent.kde.org/graphics/digikam/-/issues/10

Comment 1 Maik Qualmann 2020-09-22 11:10:24 UTC

The image that you uploaded hardly contains any metadata. Maybe these were removed by gitlab. Can you upload the photo again here?
The problem is reported from time to time, for some reason the file is probably blocked during the first scan and Exiv2 cannot read metadata (usually occurs under Windows). Try to read the metadata again (item menu-> reread metadata from file).

Maik

Comment 2 Tom de Geus 2020-09-22 11:44:27 UTC

Created attachment 131864 [details]
Problematic photo

Comment 3 Tom de Geus 2020-09-22 11:45:22 UTC

Rereading it solved the issue, thanks!

What is a bit puzzling is that the time displayed by digiKam is seemingly unrelated to the photo...?

Comment 4 Maik Qualmann 2020-09-22 11:58:40 UTC

If Exiv2 - for whatever reason - cannot decode a time, the file date is used as the last fallback.

Tested here under Windows at the moment, the correct date is also displayed after the import.

Maik

Comment 5 Tom de Geus 2020-09-22 12:06:47 UTC

That's what puzzles me. The creation dat of this file is shown by my filesystem as 

Saturday, 13 July 2019 at 12:53

However, what digiKam initially displayed was 

13.07.19 06:53

Which has seemingly no relation whatsoever with the file. 

Concerning the fallback: does exiv2 return an error? I.e. couldn't digiKam try more than once?

Comment 6 Maik Qualmann 2020-11-07 21:12:03 UTC


*** This bug has been marked as a duplicate of bug 424049 ***

Comment 7 caulier.gilles 2023-05-20 05:12:29 UTC

Problem fixed with commit listed to 

https://bugs.kde.org/show_bug.cgi?id=424049#c13

...and bugs closed :

https://bugs.kde.org/show_bug.cgi?id=465312
https://bugs.kde.org/show_bug.cgi?id=465045