I am experiencing this problem too, but I have made some tests and checks and maybe a workaround is available. I have verified while the gnome-keyring is at 100%, google chorme is recovering the stored password from Google and storing into the keyring, like they were absent. It seems google chrome was unable to use the previously stored one and pull all again from Google. I have enabled the automatic login and when google chrome starts, it asks for the password to unlock the keyring. Just avoid that and start google chrome after you have already unlocked the keyring, maybe just terminating your session and logging again with the password, skipping the automatic login.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1174162 Title: chrome-browser makes gnome-keyring-daemon use 100% cpu To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1174162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
