Date and time not recognized in old jpg, goes to 'no event', shows date&time only in extended info.
Submitted by an unknown user
Link to original bug (#719103)
Description
---- Reported by shotwell-maint@gnome.bugs 2013-11-11 06:36:00 -0800 ----
Original Redmine bug id: 7681
Original URL: http://redmine.yorba.org/issues/7681
Searchable id: yorba-bug-7681
Original author: Sven Ollino
Original description:
I have a bunch of imported images from an old computer that fail to get dated.
-
Import
-
goes to 'no event'. Notice: no date and time shown, except in extended info.
attached one of them.
Shotwell 0.15.0, Lubuntu 13.04 64bit
Related issues:
- related to shotwell - 7682: Extended Information shows file's modification time (mtim... (Open)
- related to shotwell - 3300: use file mtime as timestamp if EXIF information missing (Open)
---- Additional Comments From shotwell-maint@gnome.bugs 2013-11-11 11:10:00 -0800 ----
History
Comment 1
Updated by Jim Nelson 10 days ago
- Status changed from Open to Invalid
This photo has no Exif metadata (or any other photographic metadata for that matter) which is why this is occurring. Shotwell associates photos with events by their Exif exposure date/time field.
The date/time you're seeing in the Extended Information field is the file's modification time on the filesystem. This is a bug, which I've reported: #7682
There have been requests in the past for Shotwell to use the photo's modified time when an exposure date/time is unavailable. That's at #3300 (closed).
Comment 2
Updated by Sven Ollino 10 days ago
Ah, very well! Good job!
--- Bug imported by chaz@yorba.org 2013-11-25 21:59 UTC ---
This bug was previously known as bug 7681 at http://redmine.yorba.org/show_bug.cgi?id=7681 Imported an attachment (id=262683)
Unknown Component Using default product and component set in Parameters Unknown version " in product shotwell. Setting version to "!unspecified". Unknown milestone "unknown in product shotwell. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Resolution: RESOLVED INVALID