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

[Gunnar Hjalmarsson]

sudo explicitly says that ~/.pam_environment shall not be read;
invalidating the tasks.

** Changed in: sudo (Ubuntu)
       Status: New => Invalid

** Changed in: sudo (Ubuntu Precise)
       Status: Won't Fix => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to sudo 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:
  New
Status in “gdm” package in Ubuntu:
  Fix Released
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “openssh” package in Ubuntu:
  Triaged
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:
  In Progress
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.

  [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