Just to confirm the bug, I still see it. Here's a backtrace, if it helps: #0 0xb76a6a2a in __pthread_mutex_unlock_usercnt () from /lib/tls/i686/cmov/libpthread.so.0 #1 0xb772f55a in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #2 0xb772fae9 in ?? () from /usr/lib/libglib-2.0.so.0 #3 0x08057358 in ?? () #4 0xbf9c8a78 in ?? () #5 0x0816d698 in ?? () #6 0x00000002 in ?? () #7 0x00000002 in ?? () #8 0xb77a3a38 in ?? () from /usr/lib/libglib-2.0.so.0 #9 0xb77a3a60 in ?? () from /usr/lib/libglib-2.0.so.0 #10 0xbf9c8a74 in ?? () #11 0x00000001 in ?? () #12 0x00000001 in ?? () #13 0x08057358 in ?? () #14 0x0816d698 in ?? () #15 0xb761ba80 in ?? () from /lib/tls/i686/cmov/libc.so.6 #16 0xb76a6df0 in ?? () from /lib/tls/i686/cmov/libpthread.so.0 #17 0xb76a5520 in ?? () from /lib/tls/i686/cmov/libpthread.so.0 #18 0xb7754482 in g_thread_self () from /usr/lib/libglib-2.0.so.0 #19 0xb77301c7 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 #20 0xb78a8a93 in bonobo_main () from /usr/lib/libbonobo-2.so.0 #21 0x0804b9f2 in main (argc=134655800, argv=0xbf9c8c64) at server.c:418 #22 0xb7565450 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 #23 0x0804a3d1 in _start ()
And for further frustrational (or informational) purposes, I had logged out and logged back in from a previous session when I got e-d-s spinning at 100% CPU. -- Hangs on login and uses 100% cpu https://bugs.launchpad.net/bugs/151536 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
