GNOME Bugzilla – Bug 331537
Change time do not work if no EXIF data
Last modified: 2007-02-01 11:58:49 UTC
Please describe the problem: I had a screenshot from a few months ago, which I imported into F-Spot. I then proceeded to change the time (with just a few hours). EXIF data afterwards shows a time relative current time. Steps to reproduce: 1. Import a photo with no EXIF tags (screenshot perhaps) 2. Change the date/time with a few hours. 3. Actual results: The time is changed relative to the current time Expected results: That the time is changed relative to the photo time Does this happen every time? yes Other information: This works fine on a photo with EXIF data.
Console output below ======================= building info timer stopped: 00:00:00.0457560 3/12/2005 2:51:00 AM - 3/12/2005 1:51:03 PM = -11:00:03 time changed 00:00:00 3/12/2005 2:51:00 AM - 3/12/2005 1:51:03 PM = -11:00:03 3/12/2005 2:51:00 AM - 3/12/2005 1:51:03 PM = -11:00:03 value = f-spot version 0.1.9 len = 20 value = 2006:02:17 23:29:00 len = 19 value = 2006:02:17 23:29:00 len = 19 value = f-spot version 0.1.9 len = 20 value = 2006:02:17 23:29:00 len = 19 Saved 124 bytes saving marker Soi (null) saving marker App0 14 saving marker App1 124 saving marker App1 122 saving marker Dqt 65 saving marker Dqt 65 saving marker Sof0 15 saving marker Dht 27 saving marker Dht 103 saving marker Dht 24 saving marker Dht 47 saving marker Sos 10 new Tiff.Header timer stopped: 00:00:00.0000480 Tiff.Header.Select timer stopped: 00:00:00.0003120 building info timer stopped: 00:00:00.0125400
F-Spot only updates/adds the DateTime tag, since this tag should contain last change to the photo. But in this case, the DateTimeOriginal/DateTimeDigitized should also be updated, since they do not exist. I would also suggest (please feel free to comment) that if these two do not exist in the picture when it is added to F-Spot, these two tags are created with the file creation time stamp.
Possible related to bug #327230
The bug #331503 would fix this problem as well.
If I understand correctly, you would like the file creation date/time (as opposed to current time) to be used when there is no DateTimeOriginal metadata in the file, right? If so, then fixing 327230 will not be enough. As for the fix for #331503, it impacts only on import so does not fix this bug, does it?
Yes, if there are no meta data, you need to use the file system time stamp of the file itself. Fixing bug #327230 – SetDescription and SetDateTimeOriginal don't handle all cases , would not fix this one per say that is correct. It is a bit related though, since even if you set the exif time, it will not work since bug #327230 do not set it properly. bug #331503 - Importing photos do not keep the unix time stamp, would fix this, since the problem in this case is that F-Spot falls back to Unix File Stamp if it can not find any timestamp embedded in the photo.
This is working fine now. F-Spot adds the missing exif part in images. I'm closing the bug, reopen if you still have issues.