Systemd is triggered before user home directory is unlocked with fscrypt or ecryptfs, which results on errors with some services.

To reproduce the issue i'm using fscrypt and onedriver (home:jstaf/packages/onedriver), i've setup to automount my OneDrive storage in a directory inside my home dir. After logging in i get an error about '/etc/mtab' not having the OneDriver entry. Changing the pam.d order in /etc/pam.d/common-session fixes that.

Fscrypt README (https://github.com/google/fscrypt?tab=readme-ov-file#enabling-the-pam-module-on-other-linux-distros) advices to call pam_fscrypt.so before pam_systemd.so.

The original file is found as:
session optional        pam_systemd.so
session required        pam_limits.so   
session required        pam_unix.so     try_first_pass
session optional        pam_umask.so    
session optional        pam_fscrypt.so
(...)

It should be:
session required        pam_limits.so   
session required        pam_unix.so     try_first_pass
session optional        pam_umask.so    
session optional        pam_fscrypt.so
session optional        pam_systemd.so
(...)


EXPECTED RESULTS: The user home directory must be unlocked before trying to execute any user service. This configuration must be automatically set by pam-config.

CURRENT RESULTS: SystemD is triggered to start user services before it's home directory is unlocked, which breaks some programs.