Do

Plugins not selectable (Ubuntu 8.10 AMD64) Gnome Do 0.8 AMD64

Asked by ragnarroeck

There are no plugins in the list, except under "All Plugins", where they all show. If I tick one the tick disappears instantly, console gives me this, but the plugin functions aren't actually there:

Installing "Do.Pastebin,1.1" addin...
The following add-ins will be installed:
 - Pastebin v1.1
Installing Pastebin v1.1

ERROR: /home/USERNAME/.local/share/gnome-do/plugins-0.8.0/addins/Do.Pastebin.1.1/Pastebin.dll already exists

It is not lieing, the folder and content is generated on the first tick, but never used.

Appart from that I love gnome-do (and will use 0.6 till this gets fixed)

Question information

Language:
English Edit question
Status:
Solved
For:
Do Edit question
Assignee:
No assignee Edit question
Solved by:
ragnarroeck
Solved:
Last query:
Last reply:
Revision history for this message
Alex Launi (alexlauni) said :
#1

rm -rf ~/.local/share/gnome-do/plugins-*

--
--Alex Launi

Revision history for this message
ragnarroeck (aberrossi) said :
#2

leads to:

Installing "Do.Archive,1.0" addin...
The following add-ins will be installed:
 - Archive v1.0
Installing Archive v1.0

Assembly not found: Do.Addins, Version=0.6.0.0, Culture=neutral
WARNING: [Do.Archive,1.0] Could not load some add-in assemblies: Could not load file or assembly 'Do.Addins, Version=0.6.0.0, Culture=neutral' or one of its dependencies.

I might add I use Ubuntu in german language setting, but my useraccount name uses standard english alphabet characters. I had weird stuff going on with wrong codings, so I mention that to make sure.

Revision history for this message
Alex Launi (alexlauni) said :
#3

Looks like you have an old version of the plugins living on your system.
What version is your plugins package? Did you build from source or use a
package?

--
-- Alex Launi

Revision history for this message
ragnarroeck (aberrossi) said :
#4

Ah, there where still the 0.6 plugins installed and I saw there is a tar for the 0.8 source. Thanks for pointing that out, I will compile those and am sure that will fix it.

Revision history for this message
raboof (arnouten) said :
#5

I also had this problem installing the gnome-do-plugins package indeed solved it.

Revision history for this message
haran_elessar (david-spike) said :
#6

I'm having this exact same problem (same hardware too) but I can't figure out what you guys did to fix it. I'm a newbie of sorts, can anyone how to fix this in more detail? I went into the gnome-do folder inside share and there was a gnome-do 0.6 plugins folder...is that the problem? do I have to remove that? If so, how?

Revision history for this message
Alex Rybicki (alex-rybicki) said :
#7

Its a package maintainer problem.
Basically you downloaded gnome-do .8 from the source or deb, but when installing the gnome-do-plugins thru apt it pulls the outdated .6 plugins.
download the appropriate version from https://launchpad.net/do-plugins/+download

Revision history for this message
Alex Launi (alexlauni) said :
#8

On Fri, Feb 27, 2009 at 1:55 PM, Alex Rybicki <
<email address hidden>> wrote:

> Its a package maintainer problem.
>

This is not the case, it's entirely a user issue. In the biz we call these
ID-10t errors. If you have the repository in your sources, then there is a
0.8 plugins package; unless you're on an unsupported system, in which case
no such package exists. The 0.8 AMD64 plugins are in the PPA, they work fine
on all arches. It is only core that needs special treatment due to the
launchpad mono/buildd/xen bug (which should be fixed soon).

--
--Alex Launi

Revision history for this message
Lo Chan (fishtron) said :
#9

On AMD64, I just upgraded the do-core package from 0.6 to 0.8 with the deb since it's not in the PPA. However, subsequent updates does not automatically grab the do-plugins from apt. I have to manually grab do-plugins from apt again (sudo apt-get update && sudo apt-get install gnome-do-plugins) in order to see the 0.8 plugins.

Hope that helps!

Revision history for this message
haran_elessar (david-spike) said :
#10

thanks everyone for their input. I was able to fix my problem but it was totally unrelated to this. I have an AMD 64 but I' m using ubuntu 32-bit. I' m sorry but I did not realize that this post was about gnome-do 64 bit at the time I posted my question.

I did have the same problem though. My problem surfaced because I did a fresh install of ubuntu 8.10 on a recently fixed computer. In my haste to use gnome-do I installed and updated it before updating intrepid (which is now on a new kernel). When I updated the system and started using gnome-do I noticed it was having the plug-in problem. I proceeded to completely remove gnome-do from the system but every time I reinstalled it had the same problem and actually the same configuration. This happened even though I removed via synaptic and specifically marked it to remove everything. I also (after installing again) purged it via the terminal but I got the same result after another install.

 I ended up installing ubuntu all over again and following the correct procedure of first updating the system before updating gnome-do. Now everything works fine but I wonder...why did it " remember" its configuration after completely removing it?

Revision history for this message
whyette (whyette) said :
#11

I'm having problems with this issue. No matter how many times I tried reinstalling the plugins and the core package, I could not get the plugins to load. When can I expect to see a fix for this? I'm really hoping to get more out of this application than a spicy-looking "run" function.

Thanks!

Revision history for this message
whyette (whyette) said :
#12

Also, when I run

# sudo apt-get install gnome-do-plugins

after an update, it returns:

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.

Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
  gnome-do-plugins: Depends: libc6 (>= 2.9) but 2.8~20080505-0ubuntu9 is to be installed or
                             libc6.1 (>= 2.9) but it is not installable or
                             libc0.1 (>= 2.9) but it is not installable
                    Depends: libgconf2.24-cil (>= 2.24.0) but it is not installable
                    Depends: libglib2.0-cil (>= 2.12.7) but 2.12.1-1ubuntu2 is to be installed
                    Depends: libgnome-vfs2.24-cil (>= 2.24.0) but it is not installable
                    Depends: libgtk2.0-cil (>= 2.12.7) but 2.12.1-1ubuntu2 is to be installed
                    Depends: libmono-posix2.0-cil (>= 1.0) but it is not installable
                    Depends: libmono-system2.0-cil (>= 2.0) but 1.9.1+dfsg-4ubuntu2 is to be installed
E: Broken packages

Revision history for this message
Andreas Göransson (andgoransson) said :
#13

Confirming this is a problem.

I have installed gnome-do and gnome-do-plugins. Even reinstalled two times after completely removing the packages.

Seriously, it is not an user issue. If I use Synptic correctly i should be able to get a working software installed, everything else is disrespectful against the user, IMHO.

I am using Ubuntu 32-bit.