-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Systemd user services do not start when home dir encrypted #247
Comments
I had the same problem, solved it by editing /etc/pam.d/system-login to move the
Not sure if this is a security issue as I'm not very familiar with PAM but it seems to work fine for me. |
#270 seems to be a duplicate of this. I've created an issue on linux-pam but the don't seem to be responsible for fixing this: Here's the bug reported for Debian: |
In case it affects anyone else - on my Debian-based system, the workaround on #270 worked, but I also had to disable "lingering" for my user (the reverse of https://wiki.archlinux.org/index.php/systemd/User#Automatic_start-up_of_systemd_user_instances, ie |
My environment is Manjaro Linux with KDE as desktop environment and SDDM login manager
/etc/pam.d/passwd:
/etc/pam.d/system-login:
I created ssh-agent.service file with following content
as described here https://wiki.archlinux.org/index.php/SSH_keys#Start_ssh-agent_with_systemd_user
But after reboot and login service is inactive
ANother problem is that home dir remains unlocked after logout
The text was updated successfully, but these errors were encountered: