** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: gnome-keyring (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
An hour ago I've just had Chromium upgraded to 73.0.3683.86 (Official)
Built on Ubuntu , running on Ubuntu 16.04 (64 bit). And this started
happening.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
Same very high CPU on Ubuntu 19.04 just
after I installed, launched and logged into gmail
using browser chrome Version 73.0.3679.0 (Official Build) dev (64-bit)
After 5 mins
/usr/bin/gnome-keyring-daemon --daemonize --login
no longer used high CPU
--
You received this bug notification
This never happened in 18.04, and started happening after upgrading to
18.10. The keyring daemon when taking 100% CPU on one core also seems to
hang and not respond to applications. I've had Chrome hang on startup,
and I've had ssh and scp hang.
--
You received this bug notification because you
Olivier, I also suffer from this bug several times a day especially when
I am using IRCCloud but tonight I opened the Ubuntu Wiki in a third tab
and the CPU usage for gnome-keyring-daemon immediately rose to around
62% and stayed there for over a minute.
I'm attaching a log as you requested above
Can you open chrome://password-manager-internals/ in a tab, save the
contents of the log and share it after you reproduce the issue?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
I am having this problem. It started... yesterday? I just created a
completely new, blank browser profile, and it literally cant start due
to gnome-keyring "stuff".
its ransacking my machine.
I cant... believe this has been going on for years. I write code all
day, and the sheer level of *work*
I am seeing this and not an irccloud.com user.
On my 18.04 system with latest updates installed as of today,
gnome-keyring-daemon used up about 75-100% of CPU for more than 5 minutes (with
one chrome window open that had 6 tabs restored).
--
You received this bug notification because you are a
I am also seeing this bug, and am also an irccloud.com user. I can
confirm that if I refresh the IRCCloud tab, I see g-k-d spamming 100%
CPU for a minute or so thereafter.
I found https://bugs.chromium.org/p/chromium/issues/detail?id=777206
which is a similar-ish bug about *chrome* CPU usage on
I think I have tracked this down to irccloud.com, an app offering web
access to IRC channels once you are logged in. I had that site open in a
tab, among others, and saw `gnome-keyring-daemon` acting up. Closed
`chromium` and `gnome-keyring-daemon` stopped working. Restarted
`chromium` with the
on Ubuntu 17.04 am seeing high CPU upon launching Chrome 63.0.3239.70-1
however after about 60 seconds it finishes and CPU usage returns to normal
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
What worked for me was `gnome-keyring-daemon-old`
though
`google-chrome --password-store:basic` may work according to:
https://andreafortuna.org/chrome/how-to-prevent-the-huge-cpu-usage-of-
gnome-keyring-daemon-when-starting-google-chrome/
--
You received this bug notification because you are
I see this from time to time, according to no apparent pattern. I will
just suddenly hear my laptop fan come on, and from running `top` will
see `gnome-keyring-daemon` consuming 60–80% CPU, along with some CPU
from `chromium-browser`. The problem seems to go away on its own after a
while.
I also confirm this bug is still present in Ubuntu 17.10, on both Chrome
and Chromium.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1174162
Title:
chrome-browser makes
I have this issue on chrome Version 62.0.3202.62 and Mint Mate 17.3
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1174162
Title:
chrome-browser makes gnome-keyring-daemon
For the last few YEARS, I fix this by adding "--password-store=basic" to
the command line. It's "insecure credential storage", but it greatly
speeds up Chrome password login and no high CPU utilization.
Simply edit /usr/share/applications/google-chrome.desktop, and add
--password-store=basic to
I experience this with Chrome 63 beta and Ubuntu 16.04 all up to date as
of today.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1174162
Title:
chrome-browser makes
This drove me crazy on Ubuntu distros so I switched to Mint. It never
happens on Mint, I wonder why?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1174162
Title:
Here the same
Chrome Version 60.0.3112.113 (Offizieller Build) (64-Bit)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1174162
Title:
chrome-browser makes
Btw this is affecting also Electron (https://electron.atom.io/) apps
which try to log you in on Launch. For example Slack-Desktop.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
** Branch unlinked: lp:~cjwatson/launchpad/snap-find-by-url-prefixes
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1174162
Title:
chrome-browser makes gnome-keyring-daemon
** Branch linked: lp:~cjwatson/launchpad/snap-find-by-url-prefixes
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1174162
Title:
chrome-browser makes gnome-keyring-daemon
There is an upstream plan to trim the dependency of chromium on gnome-
keyring to a bare minimum, see
https://bugs.chromium.org/p/chromium/issues/detail?id=571003.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in
Here too, Chromium 56.0.2924.76, Ubuntu 16.04
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1174162
Title:
chrome-browser makes gnome-keyring-daemon use 100% cpu
To manage
Any news on this one? I still have this issue.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1174162
Title:
chrome-browser makes gnome-keyring-daemon use 100% cpu
To
this seems resolved, but a new issue has arisen in it's place and may be
related:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1642413
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
On my system this bug appears to have been resolved since Chromium
updated to Version 53.0.2785.143. I note that when I boot up the
system, at the log-in screen that I get a dialogue box requesting the
wireless network password which has not occurred in the past so not sure
if something has also
This has been occurring for me now for several years. I have a large
amount of passwords stored in chrome. The high CPU usage never really
stops completely, as well as anytime chrome tries to retrieve a
password, I have to wait about 10 seconds.
The fix is to rename the gnome-keyring-daemon
I found that stopping the gnome-keyring process resulted in the PC
running normally again until the screen lock came on. This resulted in
been unable to unlock the screen again requiring dropping to a command
line via Ctrl + Alt + F1 to allow a reboot.
Therefore does Petar Bojovic's ugly fix
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).
--
You received this
for me, ubuntu 1604, Google login expired, and I just login to google
account again in chrome, problem solved.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1174162
Title:
In my case, ubuntu LTS 14.04, i just turn off "automatic login" for user
ubuntu login and then after that the gnome-keyring daemon go smooth...
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
This issue just happened to me again ubuntu 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 reboot for another reason
... after boot I then launched Chrome browser Version 50.0.2661.11 dev
I have this problem only on Ubuntu with automatic login. Even ater whiping out
password db ad recreating it.
The same database makes no problem when I have to enter password before login...
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
You will lost passwords if you do
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1174162
Title:
chrome-browser makes gnome-keyring-daemon use 100% cpu
To manage
FYI. the way I fixed this was to remove the keyring subdirs from .cache
and .local/share and reboot.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1174162
Title:
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
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
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
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
** Project changed: gnome-keyring => gnome-keyring (Ubuntu)
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => High
** Changed in: gnome-keyring (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
39 matches
Mail list logo
