Error communicating with gnome-keyring-daemon

[aviramof]

Binary package hint: seahorse

i get this error "Error communicating with gnome-keyring-daemon" when i try to create a new password now not long ago i disabled the keyring password and made it unsafe because empathy keep asking for password all the time because i did not opened the keyring at startup because i am using auto login so i don't enter password when i log on and maybe as a result of
that i also can't save my isp password in network manager dsl tab in my isp profile so please check all of this and thanks in advance.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: seahorse 2.30.0-0ubuntu1
Uname: Linux 2.6.33-020633-generic i686
Architecture: i386
CheckboxSubmission: b6a081c89342ca704ad838efd83f2301
CheckboxSystem: b6505431153356bb5a118721cc51ee3f
Date: Thu Apr 1 07:43:56 2010
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100325)
ProcEnviron:
 LANG=he_IL.utf8
 SHELL=/bin/bash
SourcePackage: seahorse

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

 * Is this reproducible?
 * If so, what specific steps should we take to recreate this bug?

 This will help us to find and resolve the problem.

[aviramof (aviramof)]

it used to happen all the time before i restarted at that time there was nothing there not default not login not anything and when i tried to create a new password it gave me this error Error communicating with gnome-keyring-daemon now after restart it ok but the steps i did that might have caused it was to disable the need for password on login i disable the need for keyring password
and chose unsafe because empathy would constantly asks me for password because i did not opened the keyring in log on and
that it and i also discovered that network manager don't want to save password for my isp so i opened this thread:
http://ubuntuforums.org/showthread.php?t=1443896

and got the error while trying to do what was said there.

[aviramof (aviramof)]

and here is another problem now when i am trying to delete things from default i get an error "couldn't delete. internal error accessing gnome-keyring

[aviramof (aviramof)]

a better explination of my problem:

my problem is like this i use auto login so i don't need to enter password to login so the
first time i used empathy it asked me to unlock the keyring and enter a password i left it blank with no password and chose the unsafe option.

the problem is that many times when i open empathy it asks me for my accounts again despite the fact i entered them before but still i enter my accounts again get connected everything is fine but at a later date when i open empathy again i get an error message a line with an x the problem is that i am trying to connect to my accounts twice which is something i of course can't do so i delete the double account and the cycle go over again and again.

the cause of the problem is the keyring disappear from seahorse when this happen i open seahorse and there and there is nothing there no login no default no nothing only a message at the bottom of the screen which i am translating for you the message is:

"Error communicating with gnome-keyring-daemon" i even posted bug report about it:

[aviramof (aviramof)]

is there any news on the matter?empathy constantly asks me to enter accounts i have already entered in the past because lack of communicating with gnome-keyring-daemon.

[aviramof (aviramof)]

close this bug reported this again in a more organize manner https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/569667

[Michal (michal-ciza)]

I had the same problem and found following solution:

1. Go to System -> Preferences -> Startup Applicataions

2. Find Item: "Certificate and Key Storage" and edit it

3. Change command to: "gnome-keyring-daemon" and save it.

4. Reboot

NOTE: After upgrade from 9.10, there was following command: "gnome-keyring-daemon --start --components=pkcs11" which caused some error message. After the change mentioned above, it started working properly.