Description of problem: I cannot run gnome-d Version-Release number of selected component (if applicable): How reproducible: Run gnome-do Steps to Reproduce: 1. Run gnome-do 2. 3. Actual results: Add-in could not be loaded: The required addin 'Do.Core,1.0' is not installed. Mono.Addins.MissingDependencyException: The required addin 'Do.Core,1.0' is not installed. at Mono.Addins.AddinSessionService.ResolveLoadDependencies (System.Collections.ArrayList addins, System.Collections.Stack depCheck, System.String id, Boolean optional) [0x00000] at Mono.Addins.AddinSessionService.ResolveLoadDependencies (System.Collections.ArrayList addins, System.Collections.Stack depCheck, System.String id, Boolean optional) [0x00000] 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] Expected results: Additional info:
Hi!. Can i do something to fix it?
This issue is well known and will be fixed by me updating gnome-do to the latest versin (0.6.1.0). I am working on this and it will be ready soon.
gnome-do 0.6.1.0 depends on a new package (notify-sharp) review.
I downloaded the latest version 0.6.1.0 and when i try to run it i get this error: Add-in could not be loaded: The required addin 'Do.Core,1.0' is not installed. Mono.Addins.MissingDependencyException: The required addin 'Do.Core,1.0' is not installed. at Mono.Addins.AddinSessionService.ResolveLoadDependencies (System.Collections.ArrayList addins, System.Collections.Stack depCheck, System.String id, Boolean optional) [0x00000] at Mono.Addins.AddinSessionService.ResolveLoadDependencies (System.Collections.ArrayList addins, System.Collections.Stack depCheck, System.String id, Boolean optional) [0x00000] 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] Thanks for your help...
Good since the last update. but there is a problem with the "Files and Folders Plugin", no activation possible.
The problem with the files plugin is: Assembly not found: gconf-sharp, Version=2.20.0.0, Culture=neutral, PublicKeyToken=35e10195dab3c99f WARNING: [Do.File,1.4] Could not load some add-in assemblies: The classes in the module cannot be loaded. Also other plugins such as disk mounter fail similarly: Assembly not found: gnome-vfs-sharp, Version=2.20.0.0, Culture=neutral, PublicKeyToken=35e10195dab3c99f WARNING: [Do.DiskMounter,1.0] Could not load some add-in assemblies: The classes in the module cannot be loaded. They are all looking for the gnome-sharp 2.20 libraries, but Fedora 10 is gnome-sharp 2.24. Is this a build problem?
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This happens because the plugins you are using are downloaded and installed from upstreams plugin repository. This plugin repository uses a build system which differs in it's gnome-desktop-sharp libraries from F10. Hence the binary plugins downloaded from upstream just won't work and there's really not much I can do about it. The upcoming release of gnome-do (0.8) scheduled for release in january (I think) will move away from the central online repository to locally hosted plugins, when this happens these issues will be solveable by downstream package managers. Suggestions for workarounds welcome.
*** Bug 477995 has been marked as a duplicate of this bug. ***
*** Bug 480336 has been marked as a duplicate of this bug. ***