I can confirm the workaround is good for me too. I don't seem to need the "ProtectHostname=no" option though, and in fact, the workaround in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1916235 is also now working as well. Looking at the test system I used today it's running systemd 245.4-4ubuntu3.2, whereas the version I originally tested was 245.4-4ubuntu3.4. I'll try updating to ...3.6 and see what that does.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915502 Title: "systemd --user" fails to start for non-local users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1915502/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
