I will say that I've noticed a delay in having the network come up too, but that predates the new network-manage, and the latest systemd. It's been going on for a while now but I haven't managed to report a bug on it yet.
I have several startup apps configured in my Gnome environment, including Chromium, Emacs, Claws, and Firefox (yes, two browsers :). Immediately after a reboot and login, once say Chromium comes up, many of the pages are reporting errors that they can't get to the domain. Just visiting the tab is enough to trigger Chromium to do an auto-reload of the page, and that always works. Or if I have to manually reload, it works. There's just some small bit of time after a reboot+login where the network is inaccessible. But I don't think this is at all related to this bug. I suppose I should try to figure out which package is at fault and report a bug on it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647031 Title: systemd-resolved’s 127.0.0.53 server does not follow CNAME records To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1647031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
