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 484188 - re-import of f-spot-tagged pictures looses tags
re-import of f-spot-tagged pictures looses tags
Status: RESOLVED FIXED
Product: f-spot
Classification: Other
Component: Import
0.4.x
Other All
: Normal major
: ---
Assigned To: F-spot maintainers
F-spot maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-06 17:11 UTC by Christian
Modified: 2007-10-16 08:06 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
F-Spot-tagged picture (628.05 KB, image/jpeg)
2007-10-06 17:16 UTC, Christian
Details

Description Christian 2007-10-06 17:11:35 UTC
Please describe the problem:
I have lost my .db and tried to re-import my collection into f-spot 4.0.

It fails with the error "Object reference not set to an instance of an object".

This ALSO happens when deleting f-spot-tagged pictures from f-spot 4.0's catalogue and trying to re-import them afterwards

Steps to reproduce:
1. Tag a picture in F-Spot 4.0
2. Remove the picture from F-Spot's catalogue
3. Try to re-import that picture into F-Spot


Actual results:
Upon executing step 3 you will see the message "Import error: Object reference not set to an instance of an object

You are presented with a dialogue, giving you the option either to skip the picture or abort import.

Expected results:
Upon step 3 an import-roll should follow.

Does this happen every time?
Yes

Other information:
I have encountered this error with every single build of F-Spot 4.0 for weeks but have been hoping it would be resolved...

I have also filed this bug to Novell's Bugzilla, but no reaction from there:
https://bugzilla.novell.com/show_bug.cgi?id=304124
Comment 1 Christian 2007-10-06 17:16:41 UTC
Created attachment 96779 [details]
F-Spot-tagged picture

Any f-spot-tagged picture will fail to be re-imported into f-spot 4.0
Comment 2 Christian 2007-10-07 08:48:26 UTC
console output:


System.NullReferenceException: Object reference not set to an instance of an
object
  at FSpot.Xmp.XmpTagsImporter.ProcessStore (FSpot.MetadataStore store, .Photo
photo) [0x00000] 
  at FSpot.Xmp.XmpTagsImporter.Import (.Photo photo, System.String path,
System.String orig_path) [0x00000] 
  at FileImportBackend.Step (.Photo& photo, Gdk.Pixbuf& thumbnail,
System.Int32& count) [0x00000] 
Comment 3 Christian 2007-10-07 11:24:01 UTC
I have to make a big correction to my initial report: 

Skipped images do get imported, but they show only after re-starting f-spot and they loose their tags.

So some complaints remain:

1) Clicking 'Skip' for every single imported image after receiving an error is not a realistic way to import big numbers of images...
2) Loosing all tags is not a plus
3) Import rolls don't happen
4) Images only show up after re-starting F-Spot
Comment 4 Stephane Delcroix 2007-10-07 12:40:40 UTC
by f-spot 4.0 you mean f-spot 0.4.0 ???

compiled yourself or a packaged one ?

it should be fixed in trunk and the F_SPOT_0_4_STABLE branch. re-open if not...
Comment 5 Christian 2007-10-07 14:32:33 UTC
It is the stable 0.4.0.0-release that comes with openSUSE 10.3. See here:

http://en.opensuse.org/Product_Highlights/10.3

Also, this is the output of "f-spot --version":
F-Spot  0.4.0.0 - (c)2003-2007, Novell Inc
Personal photo management for the GNOME Desktop
Comment 6 Christian 2007-10-07 14:33:05 UTC
BTW, it is being discussed on the f-spot-mailing-list.
Comment 7 Christian 2007-10-07 14:33:46 UTC
(whoops, forget that last one)
Comment 8 Christian 2007-10-15 21:16:18 UTC
Forgot to re-open... The bug is present in the official 4.0-package that comes with openSUSE 10.3 final.

To be found here for example:
ftp://ftp5.gwdg.de/pub/opensuse/distribution/10.3/repo/oss/suse/i586/f-spot-0.4.0-35.i586.rpm
Comment 9 Stephane Delcroix 2007-10-16 08:06:24 UTC
I said "reopen if it's not fixed in F_SPOT_0_4_STABLE", not "reopen if it's not fixed in your packaged version of 0.4.0".

I don't know what patches are included in each subversions of each package for all the distro on earth... (but I'd like to) :(