GNOME Bugzilla – Bug 501652
import error: System.NullReferenceException in FSpot.Xmp.XmpTagsImporter.ProcessStore
Last modified: 2009-01-19 13:55:30 UTC
Please describe the problem: F-Spot encounters an error when attempting to import an image whose path contains a space " " character. The error message emitted is "Object reference not set to an instance of an object". Clicking on the "Skip" option appears to still import the image, though no indication is given until one views the imported images once the import has completed or been cancelled. Steps to reproduce: 1. Create an image 2a. Place image in a path with a space - or - 2b. Give the image a filename with a space in it 3. Attempt to import the image Actual results: The above described problem Expected results: No error emitted, and the image is imported without problem. Does this happen every time? Yes. Other information: This appears to be specific to Fedora 8, and not to Fedora 7.
hm. very strange. F-Spot imports fine pictures with spaces. Must be another problem. Can you please run f-spot from command line and post the lines before and after that error is printed? thanks
open uri = file:///home/basil.gohar/Pictures/2007/09/14/img_4979.jpg Error importing /home/basil.gohar/Pictures/2007/09/14/img_4979.jpg 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] Could not import file open uri = file:///home/basil.gohar/Pictures/2007/09/14/img_4980.jpg open uri = file:///home/basil.gohar/Pictures/2007/09/14/img_4980.jpg Error importing /home/basil.gohar/Pictures/2007/09/14/img_4980.jpg 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] Could not import file Stopping
I've since learned that because these pictures have been imported into another instance of F-Spot before, and I chose to store the metadata inside the files, the issue may be related to that. Is there a way I can remove the metadata from the files easily so I can test to see if this is the issue?
Can you try upgrading to 0.4.1? This same problem has been reported in bug #480861 and seems to have been fixed in the latest releases. It's not related to spaces anyway, since I see from your report that you don't have spaces neither in filename or directory. Changing summary.
Created attachment 100644 [details] F-Spot 0.4.1 compilation issues These are the last few lines from my ./configure script run. The invocation I issues was "time ./configure --prefix=$HOME/f-spot --disable-scrollkeeper". I believe the issue is related to the 64 bit platform. If I can get past this error, I should be able to successfully compile & install F-Spot 0.4.1.
I haven't been able to upgrade to 0.4.1 yet. I am running 64 bit Fedora 8, and I have been running into compilation issues. If anyone can offer some help, I'd greatly appreciate it. I've attached the issues I've been facing (since they are not directly related to this bug report's issue). I think it is related to multilib or something else related to the fact that I am running on a 64 bit platform.
In order to compile software, you have to install on your distribution the development packages of the dependencies required by F-Spot. In this case you're missing mono dev packages, which will provide the mono.pc file required for compilation. I don't know Fedora and its packaging, so you will have to figure out by yourself which package can provide that file. Please ask on IRC or on the mailing list for other compilation issues.
(In reply to comment #6) > I haven't been able to upgrade to 0.4.1 yet. Can you provide one of the failing pictures? thanks
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!