Well , this bug is frustrating. Upstream has marked bug as incomplete since : " > Unfortunately, that stack trace is missing some elements that will help a lot > to solve the problem. In particular, I need a stack trace of all threads, and > not just one (in this case the signal handling thread). "
I have narrowed down the bug to - Only happens for auto-login users. [when users enter password in policykit dialogue to unlock keyring] - Does not happen when user enters password anywhere else [in the vt or during session login.] Since this bug is tricky , i have not been able to get a full gdb. - if i start gdb from session in a terminal , i cant get back to session unless i kill the daemon. [which does not give the fully required gdb] - if i start the keyring gdb from a vt earlier[user has to enter password to login to the vt session] , then the bug wont happen! Since i have entered the password before starting keyring-daemon. It seems that user needs ssh access to system to get a full gdb. [I'm not sure I'll be able to get this done , hope someone else who has ssh access can do it] If someone can do this it would be nice. They have to remove the 3 instances of the gnome-keyring from the startup applications to start the gnome-keyring-daemon gdb and have to use the components as args. [i think since this was how i was trying to get it done] -- starts eating cpu when trying to unlock screen https://bugs.launchpad.net/bugs/524860 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
