Bug 190044 - Calendar uses (sometimes ?) 'last access' date instead of exif date
Summary: Calendar uses (sometimes ?) 'last access' date instead of exif date
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Searches-Dates (show other bugs)
Version: 0.10.0
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-19 12:00 UTC by mahikeulbody
Modified: 2016-07-15 19:05 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.1.0
Sentry Crash Report:

Attachments
picture (626.32 KB, image/jpeg)
2009-04-19 12:02 UTC, mahikeulbody 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description mahikeulbody 2009-04-19 12:00:24 UTC 
Version:           0.10.0 (using 4.2.2 (KDE 4.2.2), Kubuntu packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.28-11-generic

The attached picture is displayed in the calendar according to the last access date instead of the EXIF date.

(this picture has never been edited by Digikam)
Comment 1 mahikeulbody 2009-04-19 12:02:45 UTC 
Created attachment 32924 [details]
picture

I have others pictures driving to the same behaviour.
Comment 2 Marcel Wiesweg 2009-04-19 15:06:34 UTC 
I would assume your bug 189990 is a subset of this problem?
Comment 3 Marcel Wiesweg 2009-07-20 18:39:05 UTC 
With current 1.0 trunk this picture is displayed in the calendar for its creation date of 06/08/2000. Is this the correct date?
Comment 4 caulier.gilles 2011-12-13 12:53:32 UTC 
Mahi,

Do you see comment #3 from Marcel ?

Gilles Caulier
Comment 5 caulier.gilles 2013-11-28 22:51:04 UTC 
Mahi,

No feedback for Marcel comment #3

Gilles Caulier
Comment 6 caulier.gilles 2015-06-30 08:05:16 UTC 
New digiKam 4.11.0 is available :

https://www.digikam.org/node/740

Can you reproduce the problem with this release ?
Comment 7 caulier.gilles 2016-07-15 19:05:24 UTC 
With digiKam 5.0.0, this problem is not reproducible.
I close this file now. Don't hesitate to re-open if necessary.
Gilles Caulier