.pam_environment not applied if home directory is encrypted
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gdm3 (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
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-
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
---
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 17.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-02-08 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
Package: gdm3 3.26.1-3ubuntu3
PackageArchitec
ProcVersionSign
Tags: artful wayland-session
Uname: Linux 4.13.0-32-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
tags: |
added: bionic removed: artful |
Changed in gdm3 (Ubuntu): | |
status: | Won't Fix → Confirmed |
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 1748036
When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https:/ /wiki.ubuntu. com/ReportingBu gs.