F-Spot time zone confusion
Bug #214932 reported by
Paul Fisher
This bug report is a duplicate of:
Bug #175191: f-spot changes timestamp in an incorrect way.
Edit
Remove
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
F-Spot |
Confirmed
|
Unknown
|
|||
f-spot (Ubuntu) |
Triaged
|
Low
|
Ubuntu Desktop Bugs |
Bug Description
Binary package hint: f-spot
F-Spot appears to be unable to handle time zone conversion correctly. I had my camera set to local time (UTC−4 at the moment) and imported photos via MTP, and they were all off by four hours. I corrected them in F-Spot, and then set my camera to UTC, but then found that a newly imported photo was now eight hours off—it said it was taken at 8:00 AM when instead it was only shortly after midnight. F-Spot could perhaps store the timestamps internally as UTC, and display them in the local time zone. (I'll inspect the database and EXIF data later to see if this is already the case.)
Hardy Heron, f-spot 0.4.2
Changed in f-spot: | |
status: | Unknown → New |
Changed in f-spot: | |
assignee: | nobody → desktop-bugs |
Changed in f-spot: | |
status: | New → Confirmed |
To post a comment you must log in.
I can confirm this bug on both feisty and hardy using "stock" f-spot. Camera is set to time zone of Los_Angeles (PDT) and f-spot adds 7 hours to the images on two unrelated computers.