You are not currently logged in. If you do not have a user account then please consider creating one and logging in before you post your comment. This will allow you to track replies to your comment, and take part in the site much more freely.

To add your comment, fill in all the boxes below and then preview it to make sure you're happy with the way that it looks.

This is the comment you were replying to, attached to the weblog GNOME and libpam-mount

#4 Re: GNOME and libpam-mount Posted by dkg (216.254.xx.xx) on Mon 12 May 2008 at 17:09 I think the key insight was that the gnome-keyring pam modules do something to trigger/kick off gconfd-2, so they shouldn't be loaded until after the user's home directory is properly mounted. I'm quite sure that gconfd was not still running from a previous session, because this happened immediately after boot. /etc/pam.d/common-pammount includes both auth and session directives. So with the initial ordering of the /etc/pam.d/gdm, there's no way to cleanly insert the @include line such that it's after the common-auth and common-session, but before the gnome-keyring business. I think so, anyway. Even better would be if gnome-keyring wouldn't need access to the user's homedir, or if gconfd-2 would be able to recover more gracefully from such a sequence of events, since not everyone will use pam_mount to mount their homedir, e.g. some crypted-homedir arrangements. Thanks for thinking about this, Loic. If i can do other debugging, let me know.

Inappropriate comments will be removed.

Username:

Password:

[ Advanced Login ]

Register Account