GNOME Bugzilla – Bug 629721
Upgrading from earlier versions does not work
Last modified: 2010-09-19 13:20:50 UTC
I have been using 0.7.0, I did not install or touch addins. Then I uninstalled and installed latest from GIT. It could not start because loading addins failed. After removing ~/.config/f-spot/addin-db-001 ~/.config/f-spot/addins-setup.config it started as expected. I remember doing same procedure when upgrading from 0.6.x to 0.7.0. So these two items were generated automatically. Here is exception, which prevents loading f-spot: ikriznar@Ike-CSL:~/workspace-cpp/f-spot$ f-spot --debug ** Running f-spot in Debug Mode ** ** Running Mono with --debug ** [1 Info 00:42:01.743] Initializing Mono.Addins [1 Debug 00:42:01.812] Failed to initialize plugins, will remove addin-db and try again. [1 Warn 00:42:01.823] Caught an exception - System.InvalidOperationException: Could not read add-in description (in `Mono.Addins') at Mono.Addins.Addin.get_Description () [0x00000] at Mono.Addins.AddinSessionService.CheckHostAssembly (System.Reflection.Assembly asm) [0x00000] at Mono.Addins.AddinSessionService.ActivateRoots () [0x00000] at Mono.Addins.AddinSessionService.Initialize () [0x00000] at Mono.Addins.AddinManager.Initialize (System.String configDir) [0x00000] at FSpot.Driver.UpdatePlugins () [0x00000] in /home/ikriznar/workspace-cpp/f-spot/src/Clients/MainApp/FSpot/main.cs:300 at FSpot.Driver.InitializeAddins () [0x0000b] in /home/ikriznar/workspace-cpp/f-spot/src/Clients/MainApp/FSpot/main.cs:282 [1 Debug 00:42:03.027] Mono.Addins Initialization took 1.269039 [1 Debug 00:42:03.638] Db Initialization took 0.384234 Extension node not found in path: /FSpot/Sidebar System.InvalidOperationException: Extension node not found in path: /FSpot/Sidebar at Mono.Addins.ExtensionContext.AddExtensionNodeHandler (System.String path, Mono.Addins.ExtensionNodeEventHandler handler) [0x00000] at Mono.Addins.AddinManager.AddExtensionNodeHandler (System.String path, Mono.Addins.ExtensionNodeEventHandler handler) [0x00000] at FSpot.MainWindow..ctor (FSpot.Database.Db db) [0x00586] in /home/ikriznar/workspace-cpp/f-spot/src/Clients/MainApp/FSpot/MainWindow.cs:355 at FSpot.App.get_Organizer () [0x0003d] in /home/ikriznar/workspace-cpp/f-spot/src/Clients/MainApp/FSpot/App.cs:56 at FSpot.App.HandleOrganize () [0x0001c] in /home/ikriznar/workspace-cpp/f-spot/src/Clients/MainApp/FSpot/App.cs:234 at FSpot.App.Organize () [0x00014] in /home/ikriznar/workspace-cpp/f-spot/src/Clients/MainApp/FSpot/App.cs:102 at FSpot.Driver.Startup () [0x0013d] in /home/ikriznar/workspace-cpp/f-spot/src/Clients/MainApp/FSpot/main.cs:353 at Hyena.Gui.CleanRoomStartup.Startup (Hyena.Gui.StartupInvocationHandler startup) [0x00044] in /home/ikriznar/workspace-cpp/f-spot/lib/Hyena/Hyena.Gui/Hyena.Gui/CleanRoomStartup.cs:54 ikriznar@Ike-CSL:~/workspace-cpp/f-spot$ f-spot should be able to read or upgrade older addins configurations. I think this is critical, because it can not be expected from average user to go trough this procedure to do the upgrade.
I have just noticed I have already reported this in bug: https://bugzilla.gnome.org/show_bug.cgi?id=623193 and it should be fixed in 0.7.1. Looks like it's not fixed. Stack trace looks pretty much the same as before.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 623193 ***
I agree with you, but bug 623193 claims it's fixed, and this bug claims it's not. At leas one of these two bug reports should stay open util developers really fix the problem.
The issue in bug 623193 is fixed, as is evident from your trace (I can see it continuing past the point of failure). What you are hitting now is another failure which unfortunately, I can't reproduce. How are you running F-Spot? From a PPA? Self-compiled? Did you install it before running?
I have tried to repeat and document my situation on fresh user account and could not reproduce this problem. I have upgraded fresh config from 0.6.1.5 (or whatever Ubuntu has in repo as latest) to latest version from GIT (brand new 0.8) and worked OK. I'm not sure, what happened with those 0.7.x versions that I have been using, might have been something unclean there, but if works for 0.8, then it works.