When I attempted to setup systemd homed support for my system, I only added homed support to sys-apps/systemd (via a /etc/portage/package.use/ entry), not realizing homed support needed to be applied to the pambase package.
Taking my approach will likely cause confusion since users will not be able to authenticate their home directories properly due to pambase files in /etc/pam.d/ not being configured properly. The ideal solution is to have systemd +homed depend on pambase +homed.
This would not have occurred if homed was enabled via USE in /etc/portage/make.conf, however all users may not take this approach...
Steps to Reproduce:
1. Enable homed support on systemd
2. Be ignorant that homed support is also needed on pambase.
3. Try to login to to a home directory managed by homed.
4. Experience the unfulfilling feeling that you may be locked out of your home directory forever since you didn't make a proper backup before testing (this is a joke, didn't happen to me).
Failure to unlock the user's homed file.
Unlock homed as expected.
We need to be careful about circular deps here.
If we go by the title, bug seems to be fixed. But I'm having issue with homed, seems to be related to pam.
As Mathew instructed in first comment I enabled homed USE in make.conf and reemerged world. Home is getting unlocked at boot & everything is working well except I cant login locally via tty/console. Login via ssh works.
Please let me know if whether I should open new bug for this. Can anybody else confirm this?