Public bug reported:
Regression of bug #952185.
Variables in ~/.pam_environment are not applied when I start my computer
and login. When I then re-login, they _are_ applied.
I have manually copied my ~/.pam_environment to the original, non-
ecryptfs-mounted ~/ and then the file is always applied.
After #952185, the fix seems to have been to change debian/*.pam to run
pam_env after common-session. But I don't understand why the line in
common-auth isn't enough to mount ecryptfs. Perhaps pam_ecryptfs.so only
does the unmounting in the session phase.
Ubuntu 17.10, gdm3 3.26.1-3ubuntu3
** Affects: gdm (Ubuntu)
Importance: Undecided
Status: New
--
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/1748036
Title:
.pam_environment not applied if home directory is encrypted
Status in gdm package in Ubuntu:
New
Bug description:
Regression of bug #952185.
Variables in ~/.pam_environment are not applied when I start my
computer and login. When I then re-login, they _are_ applied.
I have manually copied my ~/.pam_environment to the original, non-
ecryptfs-mounted ~/ and then the file is always applied.
After #952185, the fix seems to have been to change debian/*.pam to
run pam_env after common-session. But I don't understand why the line
in common-auth isn't enough to mount ecryptfs. Perhaps pam_ecryptfs.so
only does the unmounting in the session phase.
Ubuntu 17.10, gdm3 3.26.1-3ubuntu3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1748036/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
