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 0x00007ffff673eb4a in times () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007ffff672e47a in clock () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x00007ffff6c8ec73 in ?? () from /lib/x86_64-linux-gnu/libgcrypt.so.11 #3 0x00007ffff6c8facd in ?? () from /lib/x86_64-linux-gnu/libgcrypt.so.11 #4 0x00007ffff6c621a0 in ?? () from /lib/x86_64-linux-gnu/libgcrypt.so.11 #5 0x00007ffff6c62d4e in ?? () from /lib/x86_64-linux-gnu/libgcrypt.so.11 After I installed the dbg package, the process was no longer stuck. Perhaps it was just stuck in a very long computation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/858775 Title: gnome-keyring-daemon hogs CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/858775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
