This bug was fixed in the package gnome-keyring - 2.26.1-0ubuntu1
---------------
gnome-keyring (2.26.1-0ubuntu1) jaunty; urgency=low
* New upstream version:
- Fix many problems with the new secure memory allocator.
(lp: #328167, #338158, #352269)
- DBus now automatically starts the gnome-keyring service properly.
(lp: #344444)
- When auto activating the gnome-keyring DBus service, check for an
already running daemon.
- Don't print critical warnings when registering with DBus fails.
- Bump glib dependency.
- Add DBus method for getting the gnome-keyring environment variables.
(lp: #345496)
- Fix crash when prompting to unlock the keyring.
- Initialize daemon with LOGNAME and USERNAME environment variables.
- Build fixes
* debian/patches/03_secure-mem_crash.patch:
- the change is in the new version
-- Sebastien Bacher <seb...@ubuntu.com> Mon, 13 Apr 2009 11:00:28
+0200
** Changed in: gnome-keyring (Ubuntu Jaunty)
Status: Won't Fix => Fix Released
--
[arm] 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
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
