After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 330785 - Problems with some photographs that have a 0000:00:00 date and time
Problems with some photographs that have a 0000:00:00 date and time
Status: RESOLVED DUPLICATE of bug 382382
Product: f-spot
Classification: Other
Component: Metadata
CVS
Other Linux
: Normal normal
: ---
Assigned To: F-spot maintainers
F-spot maintainers
Depends on:
Blocks:
 
 
Reported: 2006-02-11 13:14 UTC by Diego González
Modified: 2006-12-07 22:58 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Diego González 2006-02-11 13:14:28 UTC
i have some photographs that had a 0000:00:00 date and time exif tag, they made f-spot spew important ammount of warnings to the logs. After we got adjust time support the Date and Time (original) could be modified and some of the spew disappeared, but some of it is still shown because the Date and Time (digital) is still invalid (0000:00:00).

Shouldn't adjust time change both fields are at least be silent in these cases?

This is what i get on the console.
new Tiff.Header timer stopped: 00:00:00.0039300
error parsing 0000:00:00 00:00:00
System.ArgumentOutOfRangeException: Argument is out of range.
Parameter name: Parameters describe an unrepresentable DateTime.
in <0x00113> System.DateTime:.ctor (Int32 year, Int32 month, Int32 day, Int32 ho ur, Int32 minute, Int32 second, Int32 millisecond)
in <0x0001e> System.DateTime:.ctor (Int32 year, Int32 month, Int32 day, Int32 ho ur, Int32 minute, Int32 second)
in <0x000f4> FSpot.Tiff.DirectoryEntry:DateTimeFromString (System.String dt)
in <0x0001b> FSpot.Tiff.DirectoryEntry:get_ValueAsDate ()
in <0x008dc> FSpot.Tiff.Header:SelectDirectory (FSpot.Tiff.ImageDirectory dir, S tatementSink sink)
Tiff.Header.Select timer stopped: 00:00:00.0200580
building info timer stopped: 00:00:00.1223100
Comment 1 Bengt Thuree 2006-02-12 11:21:43 UTC
A posting by Larry on the 18 of August 2005
http://mail.gnome.org/archives/f-spot-list/2005-August/msg00077.html

>From the exif 2.2 spec

        DateTime
        The date and time of image creation. In this standard it is the
        date and time the file was changed. 
        
        DateTimeOriginal
        The date and time when the original image data was generated.
        For a DSC the date and time the picture was taken are recorded. 
        
        DateTimeDigitized
        The date and time when the image was stored as digital data. If,
        for example, an image was captured by DSC and at the same
        time the file was recorded, then the DateTimeOriginal and
        DateTimeDigitized will have the same contents. 
        
DateTime and DateTimeOriginal should be different if the image has ever
been edited.  Perhaps you were confused since in Most cases
DateTimeOriginal and DateTimeDigitized will be the same.
DateTimeDigitized is meant to be used to mark the Time Film was scanned
into a digital form, if the image started out in digital form it should
be the same as DateTimeOriginal

I very intentionally change DateTime each time the file is modified in
F-Spot.
Comment 2 Larry Ewing 2006-02-12 16:44:16 UTC
the date digitized should be adjusted when the time is adjusted, I haven't done this yet because I'm trying to come up with a better way of manipulating the metadata internally.
Comment 3 Bengt Thuree 2006-02-21 13:17:47 UTC
Partly reported in bug #327015
Comment 4 Stephane Delcroix 2006-12-07 22:58:16 UTC
Although this one is older, I mark this one as a dup of bug 382382, not because the bug id is funnier, but because we have a better test case in bug 382382.

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