I've had this problem on 3 different machines with 3 different users on 64-bit LucidLynx. I have built out these machines within the last 2 weeks. All 3 have ActiveDirectory logins (leveraging likewise-open). We do not use auto logins. They had noticed that their screen was locked, entered a password, and have waited over 30 minutes. ssh-ing in, and running top, we see that the gnome keyring-d is at 99%. If we kill that process, then the terminal lock screen seems to refresh itself, and now a password will unlock the screen immediately, as it should. I have 2 other machines that I personally use at work, they were built out with LucidLynx long before the 3 mentioned in the above(one in december, one in january), and I never had a problem as described. I'm willing to try to narrow this down, but I would have to have one of those 3 developers assist me and that may be unlikely.
-- 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
