In Lucid, Gmail docklet does not save a user's password.

I have this issue too. The terminal output is "gnome-keyring-daemon could not be reached!"

This appears when Docky is started, when clicking "Check Mail," when you open the Gmail configuration window, and twice when you enter a password.

I'm using r1165 from the ppa.

I'm seeing the same issue. Lucid 64bit.

When running docky --debug I'm seeing the error "gnome-keyring-daemon" could not be reached. Gnome-keyring-daemon is in fact running.

When I enter my full email address (google apps account) and password I get the message "Account validation succeeded!" but it does not seem to save the password. Clicking on the icon will open up my email in firefox.

As previous poster the docklet is not able to check mail and reports error "username or password not set".

I did not have this issue on Karmic.

On Lucid there may be different APIs for accessing gnome keyring and perhaps the mono library has not updated. We will look into it.

The problem here is a broken mono installation of lucid which should be fixed now. So this bug is invalid for docky.

On the other hand there is indeed an API change for gnome-keyring, but this change has been taken care of with a new libgnome-keyring implementation.

Thanks for your attention. Do you know this bug to be fixed in current packaging or did you mean in Mono svn or something?

I still have to problem on my installation, so I am wondering if I should file a bug somewhere in Ubuntu.

I have this issue too. I'm using the latest docky and the latest Lucid(32bit) .

This is an issue with Mono on Lucid. Feel free to file a bug report against Mono/Lucid.

I filed a bug report for mono in lucid, see Bug 536925!

Upstream's proclamations are flat-out wrong r.e. it being a Mono issue.

The problem is a change in libgnome-keyring, commit da22a40250da283a502ecb35add5e6548c654c6b, which removed the ability to talk to the gnome-keyring-daemon socket. This has broken gnome-keyring-sharp which interfaces with the socket, as well as all Adobe AIR apps too, for the same reason.

gnome-keyring-sharp needs to be rewritten from scratch to wrap the C library, for use on Gnome >=2.30

@directhex: hey either way, it isnt a Docky bug so little point commenting here about it. :-)

Sure, but now you can formally say "Docky doesn't work on Gnome 2.30" rather than making up vague "doesn't work on Mono" things.

I'm getting hit by this bug. Is there any movement on the gnome-keyring-sharp front to fix this?

@Robert

Could you possibly workaround this?

The workaround would be us storing your password in clear-text. So... no.

So you are going to ship a broken docklet in Lucid?

On Wed, Mar 17, 2010 at 2:55 PM, Robert Dyer <email address hidden> wrote:
> The workaround would be us storing your password in clear-text.  So...
> no.
>
> --
> In Lucid, Gmail docklet does not save a user's password.
> https://bugs.launchpad.net/bugs/529080
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Yes.

I'm running Docky 2.1.0 bzr docky r1192 ppa on Lucid and it affects me.

It affects everyone using any version of Docky on Lucid. We dont need posts of 'ya me too!'. There is *nothing* we can do about it, this is an upstream issue. Go nag them.

You could at least remove that docklet in Lucid since it doesn't work.
Unless you want to be passive-aggressive and stick it to
gnome-keyring-daemon ;)

On Thu, Mar 18, 2010 at 6:16 PM, Robert Dyer <email address hidden> wrote:
> It affects everyone using any version of Docky on Lucid.  We dont need
> posts of 'ya me too!'.  There is *nothing* we can do about it, this is
> an upstream issue.  Go nag them.
>
> --
> In Lucid, Gmail docklet does not save a user's password.
> https://bugs.launchpad.net/bugs/529080
> You received this bug notification because you are a direct subscriber
> of the bug.
>

If we remove the docklet from Lucid and the bug is fixed in the upstream package, then we can NOT add the docklet back into the Lucid Docky package. We would have to wait for the 10.10 release to add it back in. We can only push bug fixes not new features - if it was removed entirely then it would become a new feature! Whereas if we leave it in as broken, it will automatically be fixed (assuming the upstream fixed) anyway.

After the new updates that fix the Gmail applet, it now uses upwards of 70% CPU.

FYI, mpiroc claims this was fixed upstream so this issue was resolved.