I have a very similar problem on x86_64, gnome-keyring 2.25.92-0ubuntu1. Sometimes when I log in gnome-keyring-daemon is hung using 100% cpu. Sometimes it works for a while, then hangs when asked for a key by an ssh invocation. I've only had the problem since upgrading to jaunty last week.
Attaching with gdb I got the following backtrace: (gdb) bt #0 0x00007fed5df57496 in poll () from /lib/libc.so.6 #1 0x000000000046ebd0 in ?? () #2 0x00007fed5e44670f in ?? () from /usr/lib/libglib-2.0.so.0 #3 0x00007fed5e446d3d in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 #4 0x000000000040e4e7 in ?? () #5 0x00007fed5de995a6 in __libc_start_main () from /lib/libc.so.6 #6 0x000000000040dc89 in ?? () #7 0x00007fff67a59688 in ?? () #8 0x000000000000001c in ?? () #9 0x0000000000000003 in ?? () #10 0x00007fff67a5af2e in ?? () #11 0x0000000000000000 in ?? () Is there a work-around for this? My development environment is effectively unusable without an ssh key-agent, and since restarting a global agent requires logging out, I consider this a very serious issue. -- gnome-keyring-daemon eating 100% CPU at login in Jaunty https://bugs.launchpad.net/bugs/328167 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
