see also http://bugzilla.gnome.org/show_bug.cgi?id=483288
with gnome-keyring (2.20-0ubuntu4) gutsy the problem I reported is not yet solved, hereafter some more details I found out: the problem described in this bug (that is very similar to the one of GNOME bug 476644) seems to be caused by the interaction between gnome-keyring-daemon and libpam-mount, hence so few people who reported this bug (only those that use libpam-mout to mount encrypted partitions at login experience it)! I can say without any doubt that gnome-keyring works perfectly with default files /etc/pam.d/gdm and /etc/pam.d/login However if at the end of these files (and specifically /etc/pam.d/gdm) I include line @include common-pammount and reboot I get the reported problem: no keyrings are going to be loaded! and NetworkManager as well as samba and other applications keep asking for the password each time. and also gnome-keyring keeps asking also for the master password in order to create a new default keyring (which it indeed creates in $HOME/.gnome2/keyrings directory but cannot load). as I wrote in GNOME bug 483288 if I kill the gnome-keyring-daemon and then start it again having pammount enabled in both mentioned files I AM able to bring the keyring working again as expected. Unfortunately I should do this (killall then restart) at every reboot. ** Changed in: gnome-keyring (Ubuntu) Status: Fix Released => New -- gnome keyring manager cannot create permanent keyrings https://bugs.launchpad.net/bugs/146724 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs