[Bug 952185] Re: ~/.pam_environment not parsed by default

[Chris Halse Rogers]

Hello Gunnar, or anyone else affected,

Accepted lightdm into precise-proposed. The package will build now and
be available at
http://launchpad.net/ubuntu/+source/lightdm/1.2.3-0ubuntu2 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: lightdm (Ubuntu Precise)
       Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to openssh 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:
  In Progress
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