I have an XPS 13 9350 and have this problem. I found that I had both systemd-networkd and NetworkManager services enabled, but no configuration for systemd-networkd in /etc/systemd/network, and no configuration in /etc/netplan.
I noticed on a artful VM I had /etc/netplan/01-network-manager-all.yaml but not on my laptop. I created /etc/netplan/01-network-manager-all.yaml on my laptop and did 'sudo netplan apply' and rebooted, but no difference. I then looked again at my logs and saw that my wireless interface was scanning (ie, not in failed state (I was in an area with no known APs)) when systemd-networkd-wait-online finally timed out after 2 minutes. Since I knew that I use NetworkManager, I simply did `sudo systemctl disable systemd-networkd`, rebooted and had a fast boot (with NetworkManager not blocking when no known APs were available and connecting when one was). Is it intentional that systemd-networkd is enabled at the same time NetworkManager is when there is no configuration? If so, is it expected that wireless is being attempted when systemd-networkd has no configuration? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1697730 Title: Long boot time due to systemd-networkd-wait-online.service failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1697730/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
