The latest unofficial backport from the F-spot team seems to fix the
issue, at least for me: https://launchpad.net/~f-spot/+archive/f-spot-
ppa
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to f-spot in ubuntu.
https://bugs.launchpad.ne
Just to clarify, using the "time" column instead also does not return
any photos in my archive which match "time<0". Also, as I'm getting the
issue in the import dialogue box, before the images are actually
imported, it seems unlikely to be a DB error entirely.
--
You received this bug notificati
Thanks for the suggestion Mr. Cheese. Unfortunately, the photos table
doesn't have a date column:
tony@bok:~/Photos$ sqlite3 ./photos.db
SQLite version 3.7.2
Enter ".help" for instructions
Enter SQL statements terminated with a ";"
sqlite> select * from photos where date<0;
Error: no such column:
You can fix this problem temporarily by taking the following action:
1. Backup your photos.db, usually located in $HOME/.config/f-spot/photos.db
2. Install sqlite3 (apt-get install sqlite3)
3. Run: sqlite3 $HOME/.config/f-spot/photos.db
4. To find out which files are broken, do: select * from phot
I'm seeing this when opening my existing F-spot archive, which has a lot
of RAW images in it. Curiously, it only seems to affect the ones taken
on my 350D. RAW images from my 5D are fine.
I have also flushed my f-spot configuration and started again and found
the JPEG images import fine. The probl
Does anyone know how to export tags from f-spot and import them on
digiKam? I don't see other possible workaround at the moment.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to f-spot in ubuntu.
https://bugs.launchpad.net/bugs/653327
Is it possible do downgrade f-spot on Ubuntu 10.10?
--
f-spot crashes when image has wrong date
https://bugs.launchpad.net/bugs/653327
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
deskto
** Changed in: f-spot
Status: New => Unknown
--
f-spot crashes when image has wrong date
https://bugs.launchpad.net/bugs/653327
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
deskto
Oh, one more thing. My problem is that F-spot crashes on *import* as
opposed to importing fine and crashing later (as outlined in the gnone-
bugs #633020 here: https://bugzilla.gnome.org/show_bug.cgi?id=633020 )
Basically, I open f-spot, click import, select the directory on the hard
drive the pho
Mike Rose said:
"This crash has made f-spot completely and totally unusable for me."
Yeah, same here. I'm waiting for this problem to be solved because
otherwise I can't unload my pictures. Shotwell is not there yet for me
(tagging is very different, for instance.)
I'd like to suggest giving this
FWIW I'm also getting this crash with *all* of my photos taken from my
camera. Attached is one image that causes a problem.
Shotwell seems to open the images fine though.
This crash has made f-spot completely and totally unusable for me.
** Attachment added: "CRW_2607.CRW"
https://bugs.launc
All the raw (.ORF) pictures from my camera are giving me this same
error. They all show up on import with a date of 1/1/0001 even though
the jpegs are OK.
The attached .ORF is an example of a picture with this problem.
** Attachment added: "PA312764.ORF"
https://bugs.launchpad.net/ubuntu/+sou
** Changed in: f-spot
Status: Unknown => New
** Changed in: f-spot
Importance: Unknown => Medium
--
f-spot crashes when image has wrong date
https://bugs.launchpad.net/bugs/653327
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
As I can see this bug was marked incomplete at a point where there were
no confirmations. The fact that the image cannot be identified does not
mean this bug incomplete, however if you are able to find a picture, or
a series of steps to generate a picture file which will always be able
to reproduce
** Bug watch added: GNOME Bug Tracker #633020
https://bugzilla.gnome.org/show_bug.cgi?id=633020
** Also affects: f-spot via
https://bugzilla.gnome.org/show_bug.cgi?id=633020
Importance: Unknown
Status: Unknown
--
f-spot crashes when image has wrong date
https://bugs.launchpad.net
On a fresh install of Ubuntu 10.10 I am having the same problem:
[Info 23:01:07.164] Initializing Mono.Addins
Exception in Gtk# callback delegate
Note: Applications can use GLib.ExceptionManager.UnhandledException to handle
the exception.
System.ArgumentOutOfRangeException: Argument is out of
I am having the same problem trying to import JPG images. exiftool shows
nothing strange in the files, but I still get Metadata of file
file:/// may be corrupt, refusing to write to it, falling back to
XMP sidecar.
--
f-spot crashes when image has wrong date
https://bugs.launchpad.net/bugs/65
I don't think it has to do with RAW files. I just got the same issue
when trying to import jpeg images from a phone camera. Again, the exif
data shows nothing strange. If I strip the exif data from the images
before importing it works, of course.
--
f-spot crashes when image has wrong date
https:
I am experiencing the same problem, which I think stems from an import
attempt thinking some files had a date 0f 01/01/0001.
If I look in my photos dir now there it looks like:
pa...@noobuntu:~/Photos$ ls -l
total 20
drwxr-xr-x 3 paulm paulm 4096 2010-10-13 19:41 1
drwxr-xr-x 5 paulm paulm 4096
The underlying import problem seems to be something to do with raw
files, as the jpeg versions of the files imported at the same time seem
to have been imported correctly, from a dump of the photos.db:
INSERT INTO "photos"
VALUES(6042,-62135636400,'file:///home/paulm/Photos/1/01/01','IMG_3149.CR2
I get similary errors when I import picture. First, when I import:
[1 Debug 14:32:09.604] Received controller event: ImportFinished
Marshaling destroy signal
Exception in Gtk# callback delegate
Note: Applications can use GLib.ExceptionManager.UnhandledException to handle
the exception.
System.R
I really would like to, but even though I searched I could not identify the
offending image.
>From the stacktrace when run with "-v" it looks like f-spot DOES detect that
>the meta data looks bogus, but then does not handle the situation fully:
$ f-spot -verbose
[Info 01:02:03.718] Initializing
could you attach that image to the report? thanks.
** Changed in: f-spot (Ubuntu)
Importance: Undecided => Low
** Changed in: f-spot (Ubuntu)
Status: New => Incomplete
--
f-spot crashes when image has wrong date
https://bugs.launchpad.net/bugs/653327
You received this bug notification
23 matches
Mail list logo
