Applied for my next Debian upload, thanks. Sorry for the delay - I
needed to check the source rather closely to make sure this had no
unintended side-effects, since I recall this being complicated in the
past. But it looks as though this is in fact an otherwise-harmless
simplification of the path that PAM environment data takes through sshd.
** Changed in: openssh (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/952185
Title:
~/.pam_environment not parsed by default
Status in Light Display Manager:
Invalid
Status in “at” package in Ubuntu:
In Progress
Status in “gdm” package in Ubuntu:
Fix Released
Status in “lightdm” package in Ubuntu:
Fix Released
Status in “openssh” package in Ubuntu:
Fix Committed
Status in “pam” package in Ubuntu:
Invalid
Status in “sudo” package in Ubuntu:
Invalid
Status in “at” source package in Precise:
Won't Fix
Status in “gdm” source package in Precise:
In Progress
Status in “lightdm” source package in Precise:
Fix Committed
Status in “openssh” source package in Precise:
Triaged
Status in “pam” source package in Precise:
Invalid
Status in “sudo” source package in Precise:
Invalid
Bug description:
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.
[Regression Potential]
Low.
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.
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
