I don't know how it is created, but I think it is more about timing. Perhaps SSH tries to get a file handle to ~/.pam_environment and run it itself at a point in time after the encrypted home has been mounted, whereas perhaps the normal LightDM session login does so too early.
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/952185 Title: ~/.pam_environment not parsed when HOME is encrypted Status in Light Display Manager: Triaged Status in “lightdm” package in Ubuntu: Triaged Status in “pam” package in Ubuntu: In Progress Status in “lightdm” source package in Precise: Triaged Status in “pam” source package in Precise: New Bug description: I have noticed this with LightDM 1.1.6 - 1.1.8. Is HOME 'unlocked' too late? The result is that the session environment contains the system wide locale settings, while the user's locale settings are ignored. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/952185/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
