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 561900 - Timeline displays photos on wrong date after adjusting
Timeline displays photos on wrong date after adjusting
Status: RESOLVED NOTABUG
Product: f-spot
Classification: Other
Component: Browsing
0.4.x
Other All
: Normal normal
: ---
Assigned To: F-spot maintainers
F-spot maintainers
Depends on: 329588
Blocks:
 
 
Reported: 2008-11-22 09:51 UTC by Hans Persson
Modified: 2008-12-28 20:55 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Hans Persson 2008-11-22 09:51:01 UTC
Please describe the problem:
After changing the time/date on an image, I expect it to show up on the time line on the new date, but it is displayed on the old date.

Steps to reproduce:
1. Import an image.
2. Change the date.
3. Check the timeline.


Actual results:
Image shows up at old date.

Expected results:
Image should show up at new date.

Does this happen every time?
Yes.

Other information:
f-spot 0.4.3.1, Ubuntu Intrepid Ibex.
Comment 1 Stephane Delcroix 2008-11-22 20:43:54 UTC
Can you give some more explanations... on how you're checking if the image is rightly positioned on the timeline, on how you're changing the date...

I did a quick test, and it does work as expected.
Comment 2 Hans Persson 2008-11-22 22:13:28 UTC
I've imported lots of images that have incorrect dates (set to 2000 or 2008) and changed them to 2002. I don't see any images for 2002 in the timeline at all.

I'm using "Adjust time" in the Edit menu (or whatever the English translation is; I'm running in Swedish).
Comment 3 Stephane Delcroix 2008-11-23 11:59:26 UTC
this works for me. I tried with a new db, imported an image from 2005, changed its time to 2003, and the timeline was changed accordingly.

iirc, ibes contains packages for 0.5.0.3, could you please try with thoses ?
Comment 4 Hans Persson 2008-12-28 20:52:30 UTC
I had my versions confused when reporting this (wasn't running Intrepid after all). In the Intrepid version, 0.5.0.3, it works as expected. You may close this.
Comment 5 Maxxer 2008-12-28 20:55:40 UTC
in the future, as opener you can close it yourself.
thanks for testing.