A new version of f-spot has been released (v 0.6.0). I copied the old ebuild to my portage overlay and just change the version number but I get the following error when I try to start f-spot: $ f-spot ** No session dbus found. Starting one ** (/usr/lib/f-spot/f-spot.exe:26969): GLib-GObject-CRITICAL **: gtype.c:2458: initialization assertion failed, use IA__g_type_init() prior to this function (/usr/lib/f-spot/f-spot.exe:26969): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed (/usr/lib/f-spot/f-spot.exe:26969): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed Stacktrace: at (wrapper managed-to-native) GConf.Client.gconf_client_get_default () <0x00004> at (wrapper managed-to-native) GConf.Client.gconf_client_get_default () <0xffffffff> at GConf.Client..ctor () <0x00046> at FSpot.Platform.PreferenceBackend.get_Client () <0x00039> at FSpot.Platform.PreferenceBackend.AddNotify (string,System.EventHandler`1<FSpot.NotifyEventArgs>) <0x00069> at FSpot.Preferences.get_Backend () <0x00087> at FSpot.Preferences.TryGet<object> (string,object&) <0x00097> at FSpot.Preferences.Get<object> (string) <0x00043> at FSpot.Driver.Main (string[]) <0x0019b> at (wrapper runtime-invoke) FSpot.Driver.runtime_invoke_int_object (object,intptr,intptr,intptr) <0xffffffff> Native stacktrace: mono [0x80c7dc3] mono [0x80f095e] [0xb80f840c] [0xb77b4697] [0xb77b460a] [0xb77b4242] [0xb77b4110] [0xb77b3d58] [0xb77b17a4] [0xb77aa484] [0xb77aa203] mono(mono_runtime_exec_main+0x166) [0x8160a63] mono(mono_runtime_run_main+0x16e) [0x816112f] mono(mono_main+0x1b8d) [0x80b0ced] mono [0x805b50d] /lib/libc.so.6(__libc_start_main+0xe5) [0xb7e6fa65] mono [0x805b441] Debug info from gdb: ================================================================= Got a SIGSEGV while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application. ================================================================= Aborted $ I haven't found a solution to this, I ran 'emerge f-spot -e' but it didn't help. Reproducible: Always
Sorry for posting this bug, this version of f-spot can be found in portage.
