Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

After few weeks of uptime yesterday I rebooted my laptop. After that, I discovered that there is no password in gnome-keyring. gnome-keyring segfault and didn't work. I restored ~/.gnome2/keyrings/login.keyring from backup from last week, but it didn't help. gnome-keyring still segfault.

In desperation, I restored version from few months ago. It helps - gnome-keyring start working correct, but there aren't my recent passwords.

It's not a very big problem, most of passwords are up-to-date, but there is another issue. When I start google-chrome - it starts, then gnome-keyring-daemon start working with 100% CPU usage, and after few minutes - gnome-keyring slows, but google-chrome hangs - didn't respond to mouse and keybord. killall chrome helps ;)

I have read passwords from my last backup of login.keyring by simple python script and I can use it in another browser - but it's not a useful solution. Does anybody have any idea how to:

  • recover recent passwords from .keyring file which hangs gnome-keyring-daemon

  • fix connection between gnome-keyring and Google Chrome?

share|improve this question
Maybe it's related to this bug? – Stephan Vierkant Oct 1 '14 at 11:37

Ugly fix: remove gnome-keyring execute privilege.

chmod -x /usr/bin/gnome-keyring-daemon 

After this, gnome-keyring-daemon will not make any Chrome issue anymore, but it will not save any system password (google chrome password will be saved and you can used saved one too).

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.