systemd-homed incompatible with Screen Lockers

smsx · 2020-03-31 00:25:09

Hey all, recently tried to experiment with systemd-homed to create a LUKS encrypted home volume and associated user.

I've modified my pam.d as specified on the arch-wiki page, and I can log in perfectly fine.
When my screen locks - either automatically or manually - on either sway with swaylock or xfce, I can't log in again.
It seems like these screen locker programs are trying to authenticate against /etc/shadow or whatever classic method exists and aren't picking up on the pam authentication that systemd-homed is using.
Is there a simple way to get this working? an additional config file in pam.d that needs to be updated?

I don't see any error logs related to this when running

journalctl -xe

Is there a log somewhere related to authentication issues I can check? something with loginctl perhaps?

Thanks for the help!

seth · 2020-03-31 05:50:22

Like /etc/pam.d/swaylock ?

dg10a · 2020-03-31 20:45:19

Looks like this is a known issue, being tracked here: https://github.com/systemd/systemd/issues/15072

smsx · 2020-04-21 16:57:09

Thanks for the info, I had to switch back to an old school homedir and lost track of this (also uh a pandemic is distracting). Hopefully they get this resolved for v246.

heywoodlh · 2020-05-15 20:32:28

For the record -- in case anyone else is interested -- the fix has been merged into Systemd

If you're feeling bold you can install systemd-git from the AUR and screen lockers will start working again.

(If you try to install the systemd-git package from the AUR, it will fail unless you edit the PKGFILE)

Arch Linux

#1 2020-03-31 00:25:09

systemd-homed incompatible with Screen Lockers

#2 2020-03-31 05:50:22

Re: systemd-homed incompatible with Screen Lockers

#3 2020-03-31 20:45:19

Re: systemd-homed incompatible with Screen Lockers

#4 2020-04-21 16:57:09

Re: systemd-homed incompatible with Screen Lockers

#5 2020-05-15 20:32:28

Re: systemd-homed incompatible with Screen Lockers

Board footer