This bug was fixed in the package openssh - 1:5.9p1-5ubuntu1.1
---
openssh (1:5.9p1-5ubuntu1.1) precise; urgency=low
[ Gunnar Hjalmarsson ]
* debian/openssh-server.sshd.pam: Explicitly state that ~/.pam_environment
should be read, and move the pam_env calls from "auth" to "ses
This bug was fixed in the package gdm - 3.0.4-0ubuntu15.1
---
gdm (3.0.4-0ubuntu15.1) precise-proposed; urgency=low
* debian/gdm.pam, debian/gdm-autologin.pam:
Call pam_env at the end, so ~/.pam_environment is read also when
$HOME is encrypted (LP: #952185).
-- Gunnar Hjalm
I haven't actually been able to reproduce the original problem with
openssh. However, I've been able to verify that .pam_environment still
works when sshing to the account of a user with $HOME on ecryptfs after
installing the new openssh-server package from precise-proposed. Since
I'm not convinc
Hi,
I found LP#1162836 discussing this issue.
Hoping a solution will be part of 12.04 soon.
Thanks,
Erik
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/952185
Title:
~/.pam_environ
Hi,
it seems your last update form lightdm_1.2.3-0ubuntu1 to lightdm_1.2.3-0ubuntu2
with change:
* 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.
** Tags removed: verification-precise-done
** Tags added: verification-done-precise
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/952185
Title:
~/.pam_environment not parsed by defau
@Dmitrijs: Sorry, but I don't have a setup for doing so.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/952185
Title:
~/.pam_environment not parsed by default
Status in Light Display
@ gunnarhj can you test openssh as well?
** Tags removed: verification-done
** Tags added: verification-precise-done verification-precise-gdm-done
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.
I have installed gdm 3.0.4-0ubuntu15.1 från precise-proposed. When
logging in using GDM as a user with encryptfs protected $HOME, and
unlike before, the locale environment is set in accordance with
~/.pam_environment.
** Tags removed: verification-needed
** Tags added: verification-done
--
You r
** Branch linked: lp:ubuntu/precise-proposed/gdm
--
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:
Hello Gunnar, or anyone else affected,
Accepted gdm into precise-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/gdm/3.0.4-0ubuntu15.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.u
Hello Gunnar, or anyone else affected,
Accepted openssh into precise-proposed. The package will build now and
be available at
http://launchpad.net/ubuntu/+source/openssh/1:5.9p1-5ubuntu1.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https
** Branch linked: lp:~ubuntu-branches/ubuntu/raring/at/raring-proposed
--
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 Lig
This bug was fixed in the package at - 3.1.13-2ubuntu2
---
at (3.1.13-2ubuntu2) raring; urgency=low
* pam.conf:
Explicitly state that ~/.pam_environment shall be read, and move
the pam_env call to the end so it's read also when $HOME is
encrypted (LP: #952185).
-- Gunna
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
there is a new bug reported against the precise version that states that
$PATH stopped including /usr/games after the update: bug #1162836
--
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/9521
I've uploaded the gdm debdiff to Precise, thanks!
--
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:
** Branch linked: lp:ubuntu/precise-updates/lightdm
--
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:
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
hom
** Changed in: openssh (Ubuntu Precise)
Status: Triaged => In Progress
** Changed in: openssh (Ubuntu Precise)
Assignee: (unassigned) => Colin Watson (cjwatson)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm in Ubuntu.
h
** Branch linked: lp:~cjwatson/ubuntu/precise/openssh/precise-proposed
--
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 Lig
** Description changed:
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 i
This bug was fixed in the package openssh - 1:6.1p1-4
---
openssh (1:6.1p1-4) experimental; urgency=low
[ Gunnar Hjalmarsson ]
* debian/openssh-server.sshd.pam: Explicitly state that ~/.pam_environment
should be read, and move the pam_env calls from "auth" to "session" so
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
Adding a (Bazaar Explorer generated) patch for the gdm (precise) task.
** Patch added: "gdm_lp-952185_precise.patch"
https://bugs.launchpad.net/lightdm/+bug/952185/+attachment/3590171/+files/gdm_lp-952185_precise.patch
--
You received this bug notification because you are a member of Desktop
(unsubscribing sponsors, the current openssh patch is the only one
waiting for upload and Colin said he's reviewing it, so we don't need to
keep the entry in the sponsoring queue)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm in Ubu
I have installed lightdm 1.2.3-0ubuntu2 from precise-proposed and
successfully logged in with lightdm as a user with an encrypted HOME.
Now, unlike before, the locale environment is set in accordance with
~/.pam_environment.
** Tags removed: verification-needed
** Tags added: verification-done
--
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://w
This bug was fixed in the package gdm - 3.6.1-0ubuntu4
---
gdm (3.6.1-0ubuntu4) raring; urgency=low
* debian/gdm-autologin.pam:
Same changes as in debian/gdm.pam; this file was overlooked in
the fix of LP: #952185 in version 3.6.1-0ubuntu3.
-- Gunnar HjalmarssonMon, 11
** Branch linked: lp:ubuntu/precise-proposed/lightdm
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/952185
Title:
~/.pam_environment not parsed by default
Status in Light Display Man
** Branch linked: lp:ubuntu/raring-proposed/gdm
--
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:
I
** Branch linked: lp:ubuntu/lightdm
--
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
Statu
Test case added.
** Description changed:
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
@Gunnar: thanks for the work on that issue, for the SRU it would be
useful to have a testcase as well so testers know how to verify if the
fix is working as it should, could you add it to the bug summary?
--
You received this bug notification because you are a member of Desktop
Packages, which is
** Patch added: "openssh_lp-952185_raring.patch"
https://bugs.launchpad.net/lightdm/+bug/952185/+attachment/3528167/+files/openssh_lp-952185_raring.patch
** Tags added: patch
** Changed in: openssh (Ubuntu)
Status: Triaged => In Progress
** Changed in: openssh (Ubuntu)
Assignee:
** Branch linked: lp:~gunnarhj/ubuntu/raring/gdm/lp-952185
** Branch linked: lp:~gunnarhj/ubuntu/raring/at/lp-952185
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/952185
Title:
~/.p
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 Desktop
P
A Precise build of lightdm with the proposed fix is available in my PPA at
https://launchpad.net/~gunnarhj/+archive/misc
Please feel free to install, test, and report possible issues.
Closing some less important tasks.
** Description changed:
- PAM needs to be told explicitly by respective serv
** Branch linked: lp:~gunnarhj/ubuntu/precise/lightdm/lp-952185-sru
** Branch linked: lp:~gunnarhj/ubuntu/precise/gdm/lp-952185-sru
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/952185
** Bug watch removed: Debian Bug tracker #611136
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611136
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/952185
Title:
~/.pam_environ
This bug was fixed in the package gdm - 3.6.1-0ubuntu3
---
gdm (3.6.1-0ubuntu3) raring; urgency=low
* debian/gdm.pam:
Make pam_env read ~/.pam_environment (LP: #952185). This needs
to be stated explicitly, since the fix of
http://bugs.debian.org/611136 is about to make i
Fixed in lightdm 1.4.0-0ubuntu4.
** Changed in: lightdm (Ubuntu)
Status: In Progress => Fix Released
** Changed in: lightdm (Ubuntu)
Assignee: Gunnar Hjalmarsson (gunnarhj) => (unassigned)
--
You received this bug notification because you are a member of Desktop
Packages, which is s
Thanks for your guidance, Steve!
I for one understand the implications for login managers, and have
submitted merge proposals for lightdm and gdm.
** Changed in: gdm (Ubuntu)
Importance: Undecided => High
** Changed in: gdm (Ubuntu)
Status: New => In Progress
** Changed in: gdm (Ubunt
** Also affects: gdm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/952185
Title:
~/.pam_environment not parsed by default
Status
** Branch linked: lp:~gunnarhj/ubuntu/raring/gdm/pam_env
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/952185
Title:
~/.pam_environment not parsed by default
Status in Light Display
** Branch linked: lp:~ubuntu-desktop/lightdm/ubuntu
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/952185
Title:
~/.pam_environment not parsed by default
Status in Light Display Mana
** Description changed:
- I have noticed this with LightDM 1.1.6 - 1.1.8. Is HOME 'unlocked' too
- late?
+ 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 a
** Summary changed:
- ~/.pam_environment not parsed when HOME is encrypted
+ ~/.pam_environment not parsed by default
** Changed in: lightdm (Ubuntu)
Status: Triaged => In Progress
** Changed in: lightdm (Ubuntu)
Assignee: Robert Ancell (robert-ancell) => Gunnar Hjalmarsson (gunnarhj
48 matches
Mail list logo
