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

Gunnar Hjalmarsson gunnarhj at ubuntu.com
Tue Apr 2 11:39:18 UTC 2013


On 2013-04-02 11:35, Sebastien Bacher wrote:
> there is a new bug reported against the precise version that states that
> $PATH stopped including /usr/games after the update: bug #1162836

I could not reproduce that issue. Consequently, right now it seems like
that $PATH problem is related to both the fix of this bug and something
else. So we need to figure out if the fix of this bug needs to be
modified, or if it is "something else" that needs to be fixed.

-- 
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:
  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




More information about the foundations-bugs mailing list