Failure to launch on x86_64

[Allan]

When launching gnome-do on x86_64, the following error message is given

Unhandled Exception: System.InvalidOperationException: Extension node not found in path: /Do/ItemSource
  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 Do.Core.PluginManager.Initialize () [0x00000]
  at Do.Do.Main (System.String[] args) [0x00000]

This can be bypassed by repeatedly using:
rm -rf ~/.local/share/gnome-do
gnome-do

However, this fix only works occasionally and repeating it causes the problem to reappear. Possibly a race condition being hit during the setup of the ~/.local/share/gnome-do directory structure?

Further details: http://bbs.archlinux.org/viewtopic.php?pid=382616

[David Siegel (djsiegel-deactivatedaccount)]

Are you manually installing any old plugins?

[Allan (mcrae-allan)]

This occurs with no plugins installed.

[Jason Aubrey (aubreyja)]

I'm getting the same behavior. I installed gnome-do + plugins for first time directly from the Hardy Heron repositories. Can't get the fix above to work either.

Jason

Unhandled Exception: System.InvalidOperationException: Extension node not found in path: /Do/ItemSource
  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 Do.Core.PluginManager.Initialize () [0x00000]
  at Do.Do.Main (System.String[] args) [0x00000]

[Alex Launi (alexlauni)]

Can anyone confirm this with Do .5 from the PPA?

[Tobias Kappé (tobias-kappe-mail)]

I can confirm this for Do .5 from the PPA.
However, as soon as I deleted the plugins folder (rm -rf ~/.local/share/gnome-do/plugins) things started working for me again.
Hope this helps :)

[David Siegel (djsiegel-deactivatedaccount)]

I think this may be another bug related to loading plugins from an older
version of Do.

[David Siegel (djsiegel-deactivatedaccount)]

It's odd that nobody mentioned these errors from the Gentoo forums thread that prompted this bug report:

ERROR: Add-in scan operation failed. The Mono runtime may have encountered an error while trying to load an assembly.
ERROR: Add-in scan operation failed
ERROR: The add-in database could not be updated. It may be due to file corruption. Try running the setup repair utility

It looks like there's a problem in Mono.Addins that results in corrupted addin configuration, and therefore Do fails to load its plugin features.

[Cory Flick (flicck)]

Confirmed, I'm running version :

[flick@lil-spooky ~]$ pacman -Q gnome-do
gnome-do 0.6.0.0-1

on Arch Linux, 64bit, kernel :
[flick@lil-spooky ~]$ uname -r
2.6.26-ARCH

I have tried the :

This can be bypassed by repeatedly using:
rm -rf ~/.local/share/gnome-do
gnome-do

fix as well, and as others have commented, that fix only occasionally works, and Gnome-Do will, at some future point, fail to start again. I get the same Mono Addins errors as reported above when I try to run Gnome-Do from the terminal.

[Chris Halse Rogers (raof)]

Confirming, though this problem may end up being a Mono.Addins bug.

Next time someone experiences this bug, could you tar up your ~/.local/share/gnome-do/plugins directory? It's possible an analysis of the broken addin database could lead to identifying the problem.

[Aleksandar (alekrsteski)]

I have the same problem on Arch Linux x86_64. Freshly installed gnome-do 0.6.0.0 so there are no old plugins. Here is my ~/.local/share/gnome-do/plugins-0.6.0 directory.

[Allan (mcrae-allan)]

This appears to be fixed with an upgrade to mono 2.0 + rebuild of mono-addins.

[Jmadero (jmadero)]

Can you explain how to do the upgrade of mono + the rebuild. I'm using Ubuntu, got Gnome-Do 0.6 from the repos and it's giving the same error. Thanks

[David Siegel (djsiegel-deactivatedaccount)]

This is reported to be fixed in newer mono and mono.addins builds. Can someone who previously experienced this bug please try to reproduce it with a newer mono installed?

[hantheman (hantheman12)]

I get the same problem on trunk mono-addins.

[David Siegel (djsiegel-deactivatedaccount)]

Is this fixed with Do 0.8? I have no trouble on x86_64.

[Jonathan Blackhall (johnny-one-eye)]

Seems fixed to me. I also have had no problems on x86_64 using Do 0.8