This happens to me with google chrome, but not with chromiun-browser.
If i make sure all google chrome processes are killed and restart gnome-
keyring-d, it doesn't happen any more.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Just making a note about similarity between this and bug #939301; latter
perhaps a duplicate?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/858775
Title:
gnome-keyring-daemon
This bug was causing my laptop (Thinkpad T500) to overheat within 5
minutes every time I started chrome. I've bought a cooling pad but it's
not helping (the laptop still shuts itself).
I've found out that the issue does not come up when Google Chrome is not
connected with a Google account. In
Happened again, this time I had some debug info:
#0 0x7673eb4a in times () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x7672e47a in clock () from /lib/x86_64-linux-gnu/libc.so.6
#2 0x76c8ec73 in do_fast_random_poll () at random-csprng.c:1244
#3 0x76c8facd in
I can reproduce it at will by relaunching Chromium.
Here's a better stack trace with all threads:
~$ sudo ./dstack gnome-keyring-daemon
Process ID: 8460
Program name: gnome-keyring-d
Program path: /usr/bin/gnome-keyring-daemon
Thread count: 6
Dstack of gnome-keyring-d pid 8460
I'm also seeing this bug on Precise with gnome-keyring_3.2.2-2ubuntu4
and libgcrypt11_1.5.0-3ubuntu0.1.
I could get a stack trace, but unfortunately without debug symbols:
#0 0x7673eb4a in times () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x7672e47a in clock () from
** Summary changed:
- gnome-keyring-daemon hogs CPU in Oneiric
+ gnome-keyring-daemon hogs CPU
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/858775
Title:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
This happens to me when I load Google-Chrome. Once it loads, it asks me
for my password to unlock the keyring, the it's off to the races!
It doesn't seem to ever stop using 100% CPU (on my 3.4GHz Pentium D).
If I kill it, everything seems fine.
I have a fully updated Precise installation.
Is
This still happens in Precise.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/858775
Title:
gnome-keyring-daemon hogs CPU in Oneiric
Status in “gnome-keyring” package in
I have the same issue but gdm works just fine for me (clean install).
gnome-keyring-daemon uses almost 100% cpu for about 10 seconds before
stopping. It never used to do this.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring
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 Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
12 matches
Mail list logo
