*** This bug is a duplicate of bug 1174162 ***
https://bugs.launchpad.net/bugs/1174162
My best solution is to use `gnome-keyring-daemon-old`
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1433032
*** This bug is a duplicate of bug 1174162 ***
https://bugs.launchpad.net/bugs/1174162
Affecting me on latest Chromium browser and Ubuntu Mate 16.04 on a
raspberry Pi.
As if it was one more reason to go back to Firefox, this is possibly the
final nail in the coffin.
--
You received this
*** This bug is a duplicate of bug 1174162 ***
https://bugs.launchpad.net/bugs/1174162
Any news on this one? I still have this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1433032
Title:
*** This bug is a duplicate of bug 1174162 ***
https://bugs.launchpad.net/bugs/1174162
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
*** This bug is a duplicate of bug 1174162 ***
https://bugs.launchpad.net/bugs/1174162
This issue just happened to me againubuntu 16.04 ... although not
specific to that release as it happens on earlier releases too
... it was after changing my Google password
... I then needed to
*** This bug is a duplicate of bug 1174162 ***
https://bugs.launchpad.net/bugs/1174162
** This bug has been marked a duplicate of bug 1174162
chrome-browser makes gnome-keyring-daemon use 100% cpu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
My system typically runs just fine even with
~/.local/share/keyrings/login.keyring over 1.3 mb with 5000+ lines,
however CPU goes over 75% only when I setup auto login without ubuntu password
prompt on reboot.
I do get that keyring password prompt a few seconds after boot completes. Then
I can reproduce the problem with chrome but i cannot reproduce it with
chromium ... strange ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1433032
Title:
Starting Chrome makes
Well I had 50% load as well but there are two CPU threads so this is
100% of one. Clearly overloaded process. Have You tried my solution?
`gnome-keyring` has to be reinstalled from Synaptics and `Chrome` as
well but installed from a package if beta.
Regards respect.
--
You received this bug
I have noticed the same behaviour - after boot and starting chrome the
gnome-keyring-daemon process takes about 50% of CPU for about 5mins.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1433032
Reinstalled `gnome-keyring` and upgraded Chrome to v42 beta. Load time
seems decreased.
Regards respect.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1433032
Title:
Starting Chrome makes
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/1433032
I'm using Chrome Version 41.0.2272.89 (64-bit). I'm running Linux Mint
17.1 Cinnamon
I went in and removed some of the many, many stored passwords in Menu
Preferences Passwords and Keys
The ~/.local/share/keyrings/login.keyring file was 1018K before, and
765K after working through about
Hmm, important thing I should mention is that I ciphered passwords by my
own phrase not by Google default setting (Chrome preferences).
And that choking CPU is 2x 1700 MHz, one thread loaded by daemon is 1x
1700 MHz.
Regards respect.
--
You received this bug notification because you are a
14 matches
Mail list logo
