I think this is due to https://github.com/systemd/systemd/pull/30731 / 59afe07c217c73e3c7c19fb06aef2ff7bf609fd2 which was in v256-rc1.
My use case is unlocking partitions over ssh, and that commit removed the user-early handling in that case (not necessarily intentionally; ssh sessions get the tty type through a different branch, see https://github.com/systemd/systemd/blob/v256/src/login/pam_systemd.c#L1033 ). There are no local gettys at this stage either, so the user-early logic becomes not very useful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2084453 Title: systemd 256 blocks root logins before systemd-user-sessions.service is up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2084453/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
