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

[Launchpad Bug Tracker]

This bug was fixed in the package lightdm - 1.2.3-0ubuntu2

---------------
lightdm (1.2.3-0ubuntu2) precise-proposed; urgency=low

  [ Steve Langasek ]
  * Update pam configs to call pam_env last and use user_readenv=1
    explicitly, so that ~/.pam_environment can always be read even when
    home directories are encrypted with ecryptfs.  LP: #952185.
 -- Gunnar Hjalmarsson <gunnarhj at ubuntu.com>   Wed, 11 Mar 2013 23:35:00 -0700

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

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
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 Released
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 Released
Status in “openssh” source package in Precise:
  In Progress
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 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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/952185/+subscriptions