Martin, Please note, that in my setup, the network is lost immediately after rebooting with the new network-manager (1.4.2-2ubuntu4). Then, downgrading back to version 1.4.2.-2ubuntu3, and rebooting, I get network back.
In both of these versions, the network-manager creates the same kind of file /etc/resol.vconf. I only use a cable network. I do not have the package resolvconf installed, as no other package depends on it (isc-dhcp-client merely suggests it). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1638836 Title: resolv.conf for resolved stub server should have a comment how to see the actual servers Status in network-manager package in Ubuntu: Fix Released Status in resolvconf package in Ubuntu: Fix Released Bug description: resolv.conf currently just has nameserver 127.0.0.53 with resolved (its local stub resolver). We should have an extra comment on top of that that says # systemd-resolved stub resolver; run "systemd-resolve --status" to see the actual name servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
