Chromium makes gnome-keyring-daemon use 100% CPU
Posted: Tue Jun 23, 2015 1:33 pm
Shortly after Chromium starts up, gnome-keyring-daemon's CPU usage goes up to 100% and won't come down. I'd have to kill the process eventually. The negative side effect is that 'ssh-add -l' from command line reports that it can no more connect to authentication agent.
If after I killed the daemon and launch Chromium again, the daemon will be started again (I'm not sure if it's Chromium starts it again), and the cycle repeats. However, if I refuse to enter the password when the daemon asks, everything looks fine (of course, without the password, the daemon wouldn't be able to do what's it usually does).
Does anyone know what's going wrong, and how to solve/work around it?
Thanks.
If after I killed the daemon and launch Chromium again, the daemon will be started again (I'm not sure if it's Chromium starts it again), and the cycle repeats. However, if I refuse to enter the password when the daemon asks, everything looks fine (of course, without the password, the daemon wouldn't be able to do what's it usually does).
Does anyone know what's going wrong, and how to solve/work around it?
Thanks.