GNOME Bugzilla – Bug 664047
Corrupt Add-ins database causes Tomboy to fail
Last modified: 2013-01-19 23:14:02 UTC
If for some reason the add-ins DB becomes corrupt, Tomboy fails to start. The user must manually delete or rename the DB so that Tomboy can load. We should handle this gracefully. C:\Program Files (x86)\Tomboy>Tomboy.exe -debug C:\Program Files (x86)\Tomboy>[WARN 06:52:01.741] Preference key '/apps/tomboy/g lobal_keybindings/open_search' does not exist, using default. [INFO 06:52:01.913] Initializing Mono.Addins Exception in Gtk# callback delegate Note: Applications can use GLib.ExceptionManager.UnhandledException to handle the exception. System.InvalidOperationException: Could not read add-in description at Mono.Addins.Addin.get_Description() at Mono.Addins.AddinSessionService.CheckHostAssembly(Assembly asm) at Mono.Addins.AddinSessionService.ActivateRoots() at Mono.Addins.AddinSessionService.Initialize() at Mono.Addins.AddinManager.Initialize(String configDir) at Tomboy.AddinManager.InitializeMonoAddins(String old_conf_dir) in c:\Users\ grep\Development\tomboy\Tomboy\AddinManager.cs:line 93 at Tomboy.AddinManager..ctor(String tomboy_conf_dir, String old_tomboy_conf_d ir) in c:\Users\grep\Development\tomboy\Tomboy\AddinManager.cs:line 45 at Tomboy.NoteManager.Initialize() in c:\Users\grep\Development\tomboy\Tomboy \NoteManager.cs:line 134 at Tomboy.Tomboy.<>c__DisplayClass4.<Main>b__0() in c:\Users\grep\Development \tomboy\Tomboy\Tomboy.cs:line 99 at GLib.Timeout.TimeoutProxy.Handler() at GLib.ExceptionManager.RaiseUnhandledException(Exception e, Boolean is_term inal) at GLib.Timeout.TimeoutProxy.Handler() at Gtk.Application.gtk_main() at Gtk.Application.Run() at Tomboy.WindowsApplication.StartMainLoop() in c:\Users\grep\Development\tom boy\Tomboy\WindowsApplication.cs:line 87 at Tomboy.Tomboy.StartTrayIcon() in c:\Users\grep\Development\tomboy\Tomboy\T omboy.cs:line 198 at Tomboy.Tomboy.Main(String[] args) in c:\Users\grep\Development\tomboy\Tomb oy\Tomboy.cs:line 156
*** This bug has been marked as a duplicate of bug 681542 ***