On 2013-01-15 00:33, Dmitrijs Ledkovs wrote: > How is ~/.pam_environment is created?
It's created and maintained by the SetLanguage and SetFormatsLocale methods in accountsservice. > Because for example for ssh with encrypted home > ~/.ssh/authorized_keys is put outside the encrypted $HOME, not inside > it. E.g. one of the tutorials to achieve this is here: > https://rohieb.wordpress.com/2010/10/09/84/ > Such that one doesn't need to decrypt home to read > ~/.pam_environment. To me, that approach seems to be somewhat complicated to implement. Do you really think it would be better than the suggested pam solution? -- 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: Confirmed 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
