I think Dan's summary above is very good. For clarification I would add a couple of points.
The issue is not just remote logins. xdm behaves in the same way, and the absence of a systemd-logind session may mean that sound is then unavailable to the user logged in at the console. (Mentioned to help people searching for local sound issues.) Comments 12 and 16 of bug #1915502 also mention ProtectHostname=no which I don't understand. My understanding of nscd is that, even on cache misses, it will perform the lookup itself, and, being a separate process outside the systemd- logind sandbox, it will succeed. I am not convinced that mandating the use of nscd would be a good idea though, especially as some distributions are moving away from it, e.g. https://fedoraproject.org/wiki/Changes/RemoveNSCD I suspect a lot of NIS/LDAP users do use some version of nscd, which is why there are not more people caught by this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934393 Title: systemd-logind network access is blocked, and breaks remote authentication configurations To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1934393/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
