[Bug 939301] Re: Chromium and gnome-keyring, no username or password

2016-01-23 Thread iulian
** Changed in: gnome-keyring (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/939301 Title: Chromium and gnome-keyring, no username or password To

[Bug 939301] Re: Chromium and gnome-keyring, no username or password

2012-09-02 Thread Augie Schwer
From: http://karuppuswamy.com/wordpress/2010/06/18/enter-password-to- unlock-your-keyring-prompt-in-ubuntu/ What I did was to remove the old keystore with: killall -9 gnome-keyring-daemon rm -fr ~/.gnome2/keyrings and then on the first prompt to enter a new keyring password, i.e. when starting

[Bug 939301] Re: Chromium and gnome-keyring, no username or password

2012-06-08 Thread professordes
I have this issue (gnome keyring daemon hogging cpu at login with either Chrome or Chromium) on multiple machines running 12.04. No freezes, just very high cpu usage. Killing the offending process has no obvious ill effects. I'm inclined to think that the Chrome issue pointed out in #4 above,

[Bug 939301] Re: Chromium and gnome-keyring, no username or password

2012-05-12 Thread Devananda
This has happened to me repeatedly. Rebooting does not clear the issue. Some times, Chrome asks if I want to restore my previous session; clicking this leads to an error pop up, but seems to stop the run-away CPU usage by gnome-keyring-daemon. -- You received this bug notification because you

[Bug 939301] Re: Chromium and gnome-keyring, no username or password

2012-04-20 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-keyring (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/939301 Title:

[Bug 939301] Re: Chromium and gnome-keyring, no username or password

2012-04-20 Thread Dave Rolsky
This might be the same issue, or at least related - http://code.google.com/p/chromium/issues/detail?id=98601 However, I see the CPU usage simply by running chrome, and it's not just sync that freezes. Attempting to look at my list of saved passwords in settings also freezes chrome. ** Bug watch

[Bug 939301] Re: Chromium and gnome-keyring, no username or password

2012-04-19 Thread Dave Rolsky
I am seeing the same problem with Chrome. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/939301 Title: Chromium and gnome-keyring, no username or password To manage notifications about this bug go

[Bug 939301] Re: Chromium and gnome-keyring, no username or password

2012-02-22 Thread Oscar Tiderman
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/939301 Title: Chromium and gnome-keyring, no username or password To manage notifications about this bug go to: