If an account is set to auto-login - no matter if it's encrypted or not - the behaviour should be that it will autologin. The current behaviour (gdm failure) is not desirable. It would be better to explicitly disable autologin for encrypted homedirs (as suggested by Dustin) or at least for a security warning to show, preventing login (like if home perms aren't set correctly.
I notice this bug is quite old, so apologies if this isn't relevant to the current karmic development. -- GDM auto login won't work with ecryptfs https://bugs.launchpad.net/bugs/353446 You received this bug notification because you are a member of eCryptfs, which is subscribed to ecryptfs-utils in ubuntu. Status in “ecryptfs-utils” package in Ubuntu: Invalid Status in “gdm” package in Ubuntu: Confirmed Bug description: Binary package hint: gdm Using Ubuntu Jaunty Beta 1 up to date (20090401) A co-worker had trouble with the auto login in GDM, the screen kept showing a blank screen and never started gnome. So after investigating I found that he had enabled the encryptfs of his home directory. Disabling the autologin solved the problem. Steps to reproduce: 1. Install Ubuntu Jaunty choosing encripted home directory. 2. Login and select auto-login in gdmsetup. 3. Next time you try to login, the session won't start. Would it be possible that GDM informed about this or ask for the password to "unlock" the home? Maybe, with a encryptfs home one shouldn't be allowed to activate auto-login. This is related to bug 284443. _______________________________________________ Mailing list: https://launchpad.net/~ecryptfs Post to : [email protected] Unsubscribe : https://launchpad.net/~ecryptfs More help : https://help.launchpad.net/ListHelp
