By the way, this doesn't appear to be documented. IMO the existence of the pam-autologin service vs the pam-greeter service ought to be documented, as well as this behavior of setting PAM_USER in the pam- autologin service.
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1371710 Title: autologin should support PAM_USER Status in Light Display Manager: Triaged Status in Light Display Manager 1.10 series: Triaged Status in “lightdm” package in Ubuntu: Triaged Status in “lightdm” source package in Trusty: Triaged Status in “lightdm” source package in Utopic: Triaged Bug description: There should be a way to specify the autologin-user via PAM_USER. Currently, to enable autologin you specify autologin-user in the lightdm.conf file, and any value of PAM_USER returned after pam_authenticate() is ignored. This means if you want to affect autologin so that different users are logged in at different times, based on some external criteria, you must rewrite the lightdm configuration and restart the service each time. One approach would be to add a new key e.g. "autologin-user-pam=true" which would enable autologin and use the PAM_USER returned by pam_authenticate() as the user to log in. It might make sense that if PAM_USER is *not* set by the call to pam_authenticate to fall back to the autologin-user value, or else to disable autologin entirely. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1371710/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
