f-spot full crash upon startup

Status changed to 'Confirmed' because the bug affects multiple users.

It doesn't happen every time for me, although when it doesn't, f-spot won't work properly and will crash eventually.

F-Spot 0.8.2
Xubuntu 13.04
3.8.0-25-generic #37-Ubuntu SMP Thu Jun 6 20:47:07 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

It worked fine for me on 13.04 but after I imported two photos from a folder it crashed after I closed the import roll window. A couple of times it worked OK when starting with debug but now when restarting it it seems to crash every time. When starting with debug I get above backtrace.

I believe I have this fixed upstream, but there are some side effects from it that I'm trying to fix.

Had the same issue after upgrading to saucy. I uninstalled colord and f-spot works now.

F-spot works after unstalling colord as suggested by Holger

See also https://bugzilla.redhat.com/show_bug.cgi?id=903022 which looks to be the same bug.

Salient points are that it's fixed upstream, and there's a patch there for f-spot which disables the loading of cms profiles, intended as an interim measure till Stephen Shaw works out a release for the fix.

Disabling color management in f-spot seems preferable to disabling it system wide as suggested here by Jasper van der Neut

uninstalling colord as in #6 doesn't seem to work for me. I'm not entirely clear whether this is a new bug though.

I renamed .config/f-spot, and then ran f-spot and got the following. f-spot is able to get as far as putting the error in a dialog this time, though the text below is from the console.

~~~
[Info 04:23:02.657] Initializing Mono.Addins
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated.

(f-spot:15551): GLib-GObject-WARNING **: Attempt to add property __gtksharp_8_FSpot_Widgets_CellRendererTextProgress::value after class was initialised

(f-spot:15551): GLib-GObject-WARNING **: Attempt to add property __gtksharp_8_FSpot_Widgets_CellRendererTextProgress::text after class was initialised
Object reference not set to an instance of an object
System.NullReferenceException: Object reference not set to an instance of an object
  at FSpot.Widgets.PhotoImageView.LoadErrorImage (System.Exception e) [0x00000] in <filename unknown>:0
  at FSpot.Widgets.PhotoImageView.HandlePhotoItemChanged (System.Object sender, FSpot.Core.BrowsablePointerChangedEventArgs args) [0x00000] in <filename unknown>:0
  at (wrapper delegate-invoke) <Module>:invoke_void__this___object_BrowsablePointerChangedEventArgs (object,FSpot.Core.BrowsablePointerChangedEventArgs)
  at FSpot.Core.BrowsablePointer.SetIndex (Int32 value, IBrowsableItemChanges changes) [0x00000] in <filename unknown>:0
  at FSpot.Core.BrowsablePointer.HandleCollectionChanged (IBrowsableCollection collection) [0x00000] in <filename unknown>:0
  at (wrapper delegate-invoke) <Module>:invoke_void__this___IBrowsableCollection (FSpot.Core.IBrowsableCollection)
  at (wrapper delegate-invoke) <Module>:invoke_void__this___IBrowsableCollection (FSpot.Core.IBrowsableCollection)
  at FSpot.PhotoQuery.RequestReload () [0x00000] in <filename unknown>:0
  at FSpot.QueryWidget.Close () [0x00000] in <filename unknown>:0
  at FSpot.MainWindow.UpdateFindByTagMenu () [0x00000] in <filename unknown>:0
  at FSpot.MainWindow..ctor (FSpot.Database.Db db) [0x00000] in <filename unknown>:0
  at FSpot.App.get_Organizer () [0x00000] in <filename unknown>:0
  at FSpot.App.HandleOrganize () [0x00000] in <filename unknown>:0
  at FSpot.App.Organize () [0x00000] in <filename unknown>:0
  at FSpot.Driver.Startup () [0x00000] in <filename unknown>:0
  at Hyena.Gui.CleanRoomStartup.Startup (Hyena.Gui.StartupInvocationHandler startup) [0x00000] in <filename unknown>:0

(f-spot:15551): GdkPixbuf-WARNING **: GdkPixbufLoader finalized without calling gdk_pixbuf_loader_close() - this is not allowed. You must explicitly end the data stream to the loader before dropping the last reference.
~~~

Stephen, can we have an update on this? It seems to me that if we don't have a fix, then we should roll back to a working version if that's possible? Or is this about interaction with other components which have changed?