** Changed in: gnome-keyring
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/608480
Title:
libpam-gnome-keyring only uses keyrings with 'login' name
Status in GNOME keyring services:
Won't Fix
Status in “gnome-keyring” package in Ubuntu:
Triaged
Bug description:
Binary package hint: libpam-gnome-keyring
Hello folks, on lucid 10.04 with the latest updates,
pam_gnome_keyring.so only unlock the keyring using the password
provided if the keyring has 'login' name
/var/log/auth.log
Jul 21 19:13:14 folha gnome-keyring-daemon[1077]: Failed to unlock login on
startup
How to reproduce:
create a new keyring using seahorse, set it as default, move some passwords
to it (wifi password per example);
[ or you can rename it via 'mv $HOME/.gnome2/keyrings/login.keyring
$HOME/.gnome2/keyrings/default.keyring' and alter
$HOME/.gnome2/keyrings/default]
Possible solutions:
1) pam-gnome-keyring may honor $HOME/.gnome2/keyrings/default; or
2) pam-gnome-keyring must unlock each keyrings with the provided password
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-keyring/+bug/608480/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
