GNOME Bugzilla – Bug 583107
[crash] An unhandled exception was thrown: Could not read add-in description at Mono.Addins.Addin.get_Description ()
Last modified: 2012-04-28 17:39:11 UTC
Steps to reproduce: Launch banshee Stack trace: This is pushed from Fedora downstream (https://bugzilla.redhat.com/show_bug.cgi?id=501322) The user is experiencing an occasional failure to launch with the following error: An unhandled exception was thrown: 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 Banshee.ServiceStack.ServiceManager.InitializeAddins () [0x00000] at Banshee.ServiceStack.ServiceManager.DefaultInitialize () [0x00000] at Banshee.ServiceStack.Application.Initialize () [0x00000] at Banshee.Gui.GtkBaseClient.Initialize (Boolean registerCommonServices) [0x00000] at Banshee.Gui.GtkBaseClient..ctor (Boolean initializeDefault, System.String defaultIconName) [0x00000] at Banshee.Gui.GtkBaseClient..ctor () [0x00000] at Nereid.Client..ctor () [0x00000] at (wrapper managed-to-native) System.Reflection.MonoCMethod:InternalInvoke (object,object[],System.Exception&) at System.Reflection.MonoCMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000] Exception has been thrown by the target of an invocation. at System.Reflection.MonoCMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000] at System.Reflection.MonoCMethod.Invoke (BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000] at System.Reflection.ConstructorInfo.Invoke (System.Object[] parameters) [0x00000] at System.Activator.CreateInstance (System.Type type, Boolean nonPublic) [0x00000] at System.Activator.CreateInstance (System.Type type) [0x00000] at Banshee.Gui.GtkBaseClient.Startup () [0x00000] at Hyena.Gui.CleanRoomStartup.Startup (Hyena.Gui.StartupInvocationHandler startup) [0x00000] .NET Version: 2.0.50727.1433 OS Version: Unix 2.6.29.3 Assembly Version Information: System.Xml (2.0.0.0) gdk-sharp (2.12.0.0) Mono.Addins (0.4.0.0) atk-sharp (2.12.0.0) Hyena.Gui (1.4.0.0) Mono.Posix (2.0.0.0) gtk-sharp (2.12.0.0) Banshee.ThickClient (1.4.0.0) Nereid (1.4.0.0) NDesk.DBus.Proxies (0.0.0.0) Banshee.Core (1.4.0.0) System (2.0.0.0) Hyena (1.4.0.0) NDesk.DBus (1.0.0.0) glib-sharp (2.12.0.0) Banshee.Services (1.4.0.0) Banshee (1.4.0.0) mscorlib (2.0.0.0) Platform Information: Linux 2.6.29.3-140.fc11.x86_64 x86_64 x86_64 GNU/Linux Disribution Information: [/etc/fedora-release] Fedora release 11 (Leonidas) [/etc/redhat-release] Fedora release 11 (Leonidas) [/etc/system-release] Fedora release 11 (Leonidas) Other information:
I managed to fix the problem by deleting the ~/.config/banshee-1/addin-db-001 folder and all it contained. I believe some files have been corrupted somehow. I wish that Banshee could see that problem and fix it itself.
I have experienced this problem many times myself. For me, the problem stems mostly from switching between built packages (deb, rpm, etc.) to compiling and installing the official tarballs and vice verse.
*** Bug 630064 has been marked as a duplicate of this bug. ***
Confirming by the finding of dupes.
Bug 630064 includes the offending folder provided by the reporter.
Created attachment 170790 [details] Addin-db-001 Folder addin-db-001
*** Bug 647412 has been marked as a duplicate of this bug. ***
Bringing more people to the CC list from bug 647412.
Just wanted to copy&paste this comment from gabaug from bug 647412: > I'm hopeful that moving to Mono.Addins 0.6 will fix this issue in future > releases.
I think it is fixed by this commit : https://github.com/mono/mono-addins/commit/2bf0f4b5c56c56473e0a055f0f987309f3dd366a
This is indeed fixed in mono-addins by the commit linked above, which should be included in their 0.6.2 release. So I'm closing this as NOTGNOME, as it not an issue with Banshee.
*** Bug 652387 has been marked as a duplicate of this bug. ***
*** Bug 660339 has been marked as a duplicate of this bug. ***
Based on https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/768808/comments/4, this bug is still occurring in Ubuntu 12.04 with Mono.Addins 0.6.2.
Hi Chow. Both exceptions seem to be the same bug because they have the same error message, however, take a look at the stack traces: the one that I fixed in MonoAddins (fix included in 0.6.2) comes from AddinSessionService.CheckHostAssembly, however the stacktrace you just pointed out comes from TreeNode.ResetCachedData, so it is a different bug (which I've reproduced already, but much less often than the first one). So I guess we need someone to report the bug in MonoAddins tracker.