Package: ecryptfs-utils Version: 111-4 Severity: important Dear Maintainer,
After having created some systemd user units (and timers), as I have done on several other machines without issue, I noticed that the units were not started upon login on this particular machine. In fact systemctl showed no knowledge of them at all - until I reloaded the systemd user daemon and timers; after that all was fine. The difference between this machine and the other working setups: my home is encrypted via ecryptfs on this laptop. So I wondered if maybe the systemd user daemon was started upon login BEFORE my home was decrypted (thus it'd know nothing of my setup). Sure enough, in /etc/pam.d/common-session, pam_ecryptfs.so unwrap was invoked AFTER pam_systemd.so. Reversing the order fixed the problem. I don't know too much about pam but I think ecryptfs should specify a higher priority in the common-session stack. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 4.12.0-2-686-pae (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ecryptfs-utils depends on: ii gettext-base 0.19.8.1-4 ii keyutils 1.5.9-9 ii libassuan0 2.4.3-3 ii libc6 2.24-17 ii libecryptfs1 111-4 ii libgpg-error0 1.27-5 ii libgpgme11 1.9.0-6 ii libkeyutils1 1.5.9-9 ii libpam-runtime 1.1.8-3.6 ii libpam0g 1.1.8-3.6 ii libtspi1 0.3.14+fixed1-1 ecryptfs-utils recommends no packages. Versions of packages ecryptfs-utils suggests: ii cryptsetup 2:1.7.5-1 -- no debconf information
