** Description changed: lightdm precise and gdm precise SRU proposals --------------------------------------------- [Impact] As was originally stated in the bug summary, ~/.pam_environment is not read at login if $HOME is encrypted. The lightdm (Precise) and gdm (Precise) SRUs fix that issue. [Test Case] Steps to reproduce: * As a user with an ecryptfs protected $HOME, use language-selector to make the user language and/or user regional formats differ from the system wide settings (i.e. ~/.pam_environment != /etc/default/locale). - * Log out and log in again. Run the locale command from a terminal window, and you'll find that the output is a result of /etc/default/locale, i.e. ~/.pam_environment was ignored. + * Log out and log in again. Run the locale command from a terminal window, and with the old version you'll find that the output is a result of /etc/default/locale, i.e. ~/.pam_environment was ignored; with the new version ~/.pam_environment should be honoured. [Regression Potential] Low. + + openssh precise SRU proposal + ---------------------------- + As lightdm/gdm, but log in via an ssh session instead. (This can just be 'ssh localhost'.) Previous description -------------------- PAM needs to be told explicitly by respective service to parse ~/.pam_environment, since the fix of http://bugs.debian.org/611136 is about to make it into Raring. Please see comment #29 and #30. Otherwise the session environment will contain the system wide locale settings, while the user's locale settings are ignored.
-- 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/952185 Title: ~/.pam_environment not parsed by default To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/952185/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
