GNOME Bugzilla – Bug 624313
AddinManager sometimes fails to initialize.
Last modified: 2010-07-22 16:52:46 UTC
f-spot --debug ** Running f-spot in Debug Mode ** ** Running Mono with --debug ** [1 Info 11:11:33.477] Initializing Mono.Addins Unhandled Exception: System.InvalidOperationException: Could not read add-in description 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.InitializeAddins () [0x0000b] in /home/dave/Desktop/f-spot-0.7.1/src/main.cs:280 at FSpot.Driver.Main (System.String[] args) [0x002c8] in /home/dave/Desktop/f-spot-0.7.1/src/main.cs:246
<tigger> you may reset (delete) the addin-folder that worked for me. <rubenv> we should do that automatically <rubenv> if addin initialization fails => delete the addin-db and retry
with latest release I cannot seem to keep addins working. I need to enable/disable each export at every run. deleting .config/f-spot/addin* won't solve here.
Done.
(In reply to comment #2) > with latest release I cannot seem to keep addins working. > I need to enable/disable each export at every run. > deleting .config/f-spot/addin* won't solve here. Please open a different bug for that, this is about initialization failure crashers.