Robert: does this mean that bug 753707 was introduced? It seems that autologin now does not work when .ecryptfs is present in the $HOME directory of the user to be autologged in.
If I can add my two cents, that seems to be a bit unfortunate, because now gdm does not ask me for password anyway (it just wants me to select myself as the user to be logged in) so the encrypted directory is not mounted anyway and autlogin does not work either. There is a README in my Private directory that reads as follows: THIS DIRECTORY HAS BEEN UNMOUNTED TO PROTECT YOUR DATA. >From the graphical desktop, click on: "Access Your Private Data" or >From the command line, run: ecryptfs-mount-private Why don't we change it so something like this (I am not a native speaker so the English might be dubious, I am not sure if autlogin can be made into a verb) : THIS DIRECTORY HAS BEEN UNMOUNTED TO PROTECT YOUR DATA. This may be because you were autologged in and thus did not enter your password. >From the graphical desktop, click on: "Access Your Private Data" or >From the command line, run: ecryptfs-mount-private -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/284443 Title: gdmsetup: Don't offer autologin for ecryptfs users -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
