This bug was fixed in the package gnome-keyring - 2.25.92-0ubuntu1
---------------
gnome-keyring (2.25.92-0ubuntu1) jaunty; urgency=low
* New upstream version:
- Fix problems when multiple processes tried to initialize the
gnome-keyring-daemon at the same time, often resulting in a user
session that hung on login.
- Add compatibility support for loading SSH unlock passwords from
previous versions of gnome-keyring.
- Fix compiler warnings on 32-bit systems.
- Fix uninitialized variable usage. These resulted in crashes.
- Initialize PKCS#11 tokens before importing certificates or keys
to them. Remove previous auto-initialize idea.
- Add basic support for PKCS#11 SO logins.
- Fix focus issues in the import certificate/key dialog.
- When looking for PKCS#11 objects, skip tokens that have not been
initialized.
- Exit properly when an error occurs on importing a certificate or key.
- Hash objects when storing them in PKCS#11 user-store and
validate the hashes when loading them.
- Build fix on Solaris
- If login keyring doesn't exist when changing a PAM password, don't
create it automatically.
- Close stdin/stdout when not running the daemon in foreground. This
fixes a regression in scripts starting gnome-keyring-daemon. (lp: #316070)
-- Sebastien Bacher <[email protected]> Mon, 02 Mar 2009 17:00:10
+0100
** Changed in: gnome-keyring (Ubuntu)
Status: Fix Committed => Fix Released
--
gnome-keyring-daemon's output cannot be sourced anymore
https://bugs.launchpad.net/bugs/316070
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
