** Changed in: f-spot
Importance: Unknown = High
--
f-spot changes timestamp in an incorrect way
https://bugs.launchpad.net/bugs/175191
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to f-spot in ubuntu.
--
desktop-bugs mailing list
This bug was fixed in the package f-spot - 0.6.1.5-2ubuntu7
---
f-spot (0.6.1.5-2ubuntu7) lucid-proposed; urgency=low
[ Martin Mai ]
* debian/patches/git_dont_delete_emailed_files_after_a_fixed_time-out.patch:
+ Leave it up to the os to clear emailed files in /tmp/ (LP:
SRU Verification for Lucid:
I have reproduced the problem with f-spot 0.6.1.5-2ubuntu6 and have verified
that the version of f-spot 0.6.1.5-2ubuntu7 in -proposed fixes the issue.
Marking as verification-done
** Tags added: verification-done
** Tags removed: verification-needed
--
f-spot
Accepted f-spot into lucid-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Tags added: verification-needed
--
** Branch linked: lp:ubuntu/lucid-proposed/f-spot
--
f-spot changes timestamp in an incorrect way
https://bugs.launchpad.net/bugs/175191
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to f-spot in ubuntu.
--
desktop-bugs mailing list
Pushed to -proposed:
f-spot (0.6.1.5-2ubuntu7) lucid-proposed; urgency=low
[ Martin Mai ]
* debian/patches/git_dont_delete_emailed_files_after_a_fixed_time-out.patch:
+ Leave it up to the os to clear emailed files in /tmp/ (LP: #112684)
[ Didier Roche ]
*
** Patch added: 0.6.1.5-2ubuntu6_2_0.6.1.5-2ubuntu7.debdiff
http://launchpadlibrarian.net/50423951/0.6.1.5-2ubuntu6_2_0.6.1.5-2ubuntu7.debdiff
--
f-spot changes timestamp in an incorrect way
https://bugs.launchpad.net/bugs/175191
You received this bug notification because you are a member
** Changed in: f-spot (Ubuntu Lucid)
Assignee: Chris Halse Rogers (raof) = Didier Roche (didrocks)
** Changed in: f-spot (Ubuntu Lucid)
Status: Fix Released = Fix Committed
--
f-spot changes timestamp in an incorrect way
https://bugs.launchpad.net/bugs/175191
You received this bug
Well I am a more than a little confused... So I see that F-Spot does
not appear to change the exif information of my pictures but importing
them still causes the time shift on the date/time when viewed in the
program and in the creation of the folder archive. This is a very minor
improvement to
The current fix in Ubuntu's released version doesn't entirely solve
the problem. It *is* solved in 0.6.2, the new upstream release. They
essentially just incorporated the same patch my PPA package uses into
the mainline code.
I will attempt to keep my PPA packages up to date as time permits,
** Changed in: f-spot
Status: Confirmed = Fix Released
--
f-spot changes timestamp in an incorrect way
https://bugs.launchpad.net/bugs/175191
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to f-spot in ubuntu.
--
desktop-bugs
0.6.2 has quite some changes, it will be consider for a sru but it might
take some time
--
f-spot changes timestamp in an incorrect way
https://bugs.launchpad.net/bugs/175191
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to f-spot in
This is now fixed for real in the new upstream version 0.6.2, using the
patch that I was advocating by Paul Wellner Bou.
The new version simply does not alter EXIF timestamps, which is arguably
the correct behavior.
What are the chances of seeing 0.6.2 in current Ubuntu as an SRU?
--
f-spot
This bug was fixed in the package f-spot - 0.6.1.5-2ubuntu5
---
f-spot (0.6.1.5-2ubuntu5) lucid; urgency=low
* debian/patches/ubuntu_add_save_and_undo.patch:
+ Save over existing files more safely.
+ Save orientation where possible.
*
** Branch linked: lp:ubuntu/f-spot
--
f-spot changes timestamp in an incorrect way
https://bugs.launchpad.net/bugs/175191
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to f-spot in ubuntu.
--
desktop-bugs mailing list
** Changed in: f-spot (Ubuntu Lucid)
Assignee: Canonical Desktop Team (canonical-desktop-team) = Chris Halse
Rogers (raof)
--
f-spot changes timestamp in an incorrect way
https://bugs.launchpad.net/bugs/175191
You received this bug notification because you are a member of Ubuntu
Desktop
This hacking of my exif timestamps is affecting me in show-stopping
ways. F-spot needs to offer a checkbox to turn this off, otherwise I
must discontinue using it. I'll also have to warn everyone else about
it too, in case it effects something they're doing too. Why can't this
be fixed?
--
It looks to me like this could be fixed by simply not writing out
EXIF.OriginalDateTime to the first version of the file (named
Original) imported by F-Spot. That version is marked as protected,
and should be read-only anyway.
As far as I can tell, F-Spot only reads the tags once, on import, and
** Also affects: f-spot (Ubuntu Lucid)
Importance: High
Assignee: Ubuntu Desktop Bugs (desktop-bugs)
Status: Triaged
** Changed in: f-spot (Ubuntu Lucid)
Assignee: Ubuntu Desktop Bugs (desktop-bugs) = Canonical Desktop Team
(canonical-desktop-team)
--
f-spot changes
Just to ping this bug and stress its importance:
Lucid release is near and Ubuntu is shipping (again) a photo manager
(its official photo manager...) with a critical bug which cause
(VOLUNTARY) DATA CORRUPTION. Yes, data corruption: no other definition
possible, because the software do not tell
The issue on this one is not to think about the issue it's to understand
why f-spot does the things the way it does now. The suggested change
before seems to change code over the import tags update. What would the
changes mean for already imported photos, does anybody why f-spot try to
change the
As far I understood, developers want enforce an absolute order in the
photo collection, so that photos are displayed in real shoot order (a
photo taken at 1.00 PM in London would be displayed after a photo taken
at 1.30 PM in Rome). Is that useful? I think it is completely not:
(almost) no one
Today I found this open letter (http://daniel-
bartholomew.com/wordpress/2009/10/f-spot-considered-harmful/) to F-spot
devs. Perhaps it is time to address this issue.
To whom it may concern,
Data corruption is ALWAYS a critical problem but you list bugs 340903
and 454082 as “UNCONFIRMED” with a
Thank you for bringing this bug to our attention. However, a paper cut
should be a small usability issue , in the default Ubuntu 9.10 install ,
that affects many people and is quick and easy to fix. So this bug can't
be addressed as part of the project.
not a paper cut read comment#10 upstream
Thank you for bringing this bug to our attention. However, a paper cut
should be a small usability issue , in the default Ubuntu 9.10 install ,
that affects many people and is quick and easy to fix. So this bug can't
be addressed as part of the project.
not a paper cut read comment#10 upstream
Hi,
Thank you for the package! Imports no longer get modified! :-)
However... there is still one problem left:
After correcting the already imported pictures with the command
exiftool -r -CreateDateDateTimeOriginal -overwrite_original
FOLDERNAME
the time inside the exif-data is all right, but
The only (easy) way to get the times right in F-Spot's DB again is to
remove and re-import your pictures, unfortunately.
It would be possible to modify the times in the DB directly, a script
could be written to adjust them behind F-Spot's back, but that's a
little beyond me right now.
Google
** Also affects: hundredpapercuts
Importance: Undecided
Status: New
--
f-spot changes timestamp in an incorrect way
https://bugs.launchpad.net/bugs/175191
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs
Thank you a lot Steve for the modified package.
F-spot behaviour of incorrectly modifying the exif data is annoying.
--
f-spot changes timestamp in an incorrect way
https://bugs.launchpad.net/bugs/175191
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
comments about dropping default applications to universe because of a
bug are not really constructive suggestions there
--
f-spot changes timestamp in an incorrect way
https://bugs.launchpad.net/bugs/175191
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Maybe this isn't the right place for that particular discussion, but the
discussion should be had somewhere, and I don't see how it could end any
other way than either for f-spot to be fixed or for it to drop to
universe/multiverse. It's simply unacceptable that a default application
knowingly
I've posted a link to Steve's patch upstream.
I do think that Ubuntu needs to address this (locally or backported from
upstream), or f-spot bumped to universe. Products with data loss bugs
affecting a large number of users that have been open for 6 years don't
really belong in main.
--
f-spot
I'm attaching the patch I'm using for F-Spot to not automatically adjust
timestamps. Just in case Ubuntu ever wants to just temporarily fix this
downstream for now, or if anyone just wants to take a look and hack
away.
This is the patch I'm using in my PPA packages of F-Spot, it applies
cleanly
For all those who are interested, I am currently testing an Ubuntu
package of F-Spot which is patched to not alter timestamps, except when
asked to do so via the usual Adjust Time... dialog.
This is a standard Ubuntu Karmic build of F-Spot 0.6.1.4, with all
automatic timestamp altering removed.
why couldn't that go upstream too?
--
f-spot changes timestamp in an incorrect way
https://bugs.launchpad.net/bugs/175191
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
to reply to the question ubuntu is not likely to use a change not
accepted by GNOME on this issue
--
f-spot changes timestamp in an incorrect way
https://bugs.launchpad.net/bugs/175191
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
In regards to #18, The F-Spot developers do not agree with the Don't
automatically alter timestamps solution.
They are working to develop a solution where F-Spot will alter timestamps in a
correct way.
This is the reason for my question, to see if this issue could at least
be fixed within
I agree that this bug has gone on for way too long for something so
trivially fixable; I would half tempted to flex my C# coding skills on
this one if there was a hope of any such patch being accepted.
--
f-spot changes timestamp in an incorrect way
https://bugs.launchpad.net/bugs/175191
You
For anyone who needs to restore the original EXIF dates and times
without restoring from backup, the following command should do it.
exiftool -r -CreateDateDateTimeOriginal *.jpg
(-r option for recursing into lower directories)
Taken from this comment at Gnome Bugzilla:
The exiftool method is what I used to fix my corruption. Unfortunately I
had some photos that had already been adjusted because my camera had the
wrong date set for quite a long time. I forget the exact steps I took,
but the end result was all of my photos being off by at least a couple
hours.
I had some thoughts on this earlier today, as I was manually correcting
the timestamp on about 2,000 photos that F-Spot chose to corrupt for me.
I'm commenting here because I believe that something should be done
about this in Ubuntu until upstream comes up with a solution. I'm not
holding my
for this bugs it's better to comment on the upstream bug tracker, please
do it at http://bugzilla.gnome.org/show_bug.cgi?id=332025, will raise
the priority of the upstream bug as well, thanks you.
--
f-spot changes timestamp in an incorrect way
https://bugs.launchpad.net/bugs/175191
You received
** Changed in: f-spot
Status: New = Confirmed
--
f-spot changes timestamp in an incorrect way
https://bugs.launchpad.net/bugs/175191
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
I second bododod's comments - I have put up with this bug for over a
year now. It is especially bad for someone who then want's to correlate
GPS data (geotag) there photos.
How can we get this bug fixed before Jaunty?
--
f-spot changes timestamp in an incorrect way
Is anything being done about this? F-Spot is touted as a major feature of
Ubuntu:
http://www.ubuntu.com/products/whatisubuntu/810features/photos/
but this bug ruins date and time data attached to imported photos, and
for good. It makes F-Spot completely unusable for me since I want this
Since this bug corrupts user data I think it should probably have a
higher importance than Low.
--
f-spot changes timestamp in an incorrect way
https://bugs.launchpad.net/bugs/175191
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
I don't know how to link this to more bugs in the gnome bugzilla, but here are
a few more bugs that are basically duplicates (although not marked as such):
http://bugzilla.gnome.org/show_bug.cgi?id=329588
http://bugzilla.gnome.org/show_bug.cgi?id=340899
This bug has been open upstream for over 2.5 years now.
Can we get one of the unofficial patches into Ubuntu?
--
f-spot changes timestamp in an incorrect way
https://bugs.launchpad.net/bugs/175191
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
Also:
http://bugzilla.gnome.org/show_bug.cgi?id=480615
http://bugzilla.gnome.org/show_bug.cgi?id=532668
I'm bumping importance - it seems to fulfill the criteria of a high
importance task due to data loss - Has a severe impact on a small
portion of Ubuntu users (estimated). I suspect it is a
I believe we have actually two bugs here:
1) some dates aren't converted correctly when displayed, and
2) the EXIF DateTimeOriginal is modified even though f-spot should never modify
it automatically.
Now, 1 is annoying but not really that bad, whereas 2 is what corrupts
the user's data and is
** Changed in: f-spot (Ubuntu)
Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs)
--
f-spot changes timestamp in an incorrect way
https://bugs.launchpad.net/bugs/175191
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
Looks like this is going to affect Intrepid too :-(
No 'correct' fix from upstream yet. There are a couple of unofficial
patches, but I don't think they have been packaged for Ubuntu.
--
f-spot changes timestamp in an incorrect way
https://bugs.launchpad.net/bugs/175191
You received this bug
Is this currently being worked on in upstream? As far as I can tell, it
will still affect Hardy.
--
f-spot changes timestamp in an incorrect way
https://bugs.launchpad.net/bugs/175191
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
53 matches
Mail list logo
