Maybe this behaviour should be tied for example into one installing ubuntu-desktop package or equivalent? While it is true that for example in server machine having NetworkManager and it controlling stuff is generally not wanted behaviour, but when user install ubuntu in "not official" way, like debootstrap that is needed for "ZFS as root partition" installation currently, all user has first is base minimum setup and then if wanted to install ubuntu GUI, one uses basically "apt- get install ubuntu-desktop"... I think that should be deciding factor to have NM managing devices or not.
In any way, if NM is managing devices, an update in general should not change that, or ofcourse other way round too, status quo should stay. -- 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/1658921 Title: NetworkManager does not manage wired connection Status in network-manager package in Ubuntu: Confirmed Bug description: NetworkManager does not manage my wired eth0 connection, no matter how I set /etc/network/interfaces or /etc/NetworkManager/NetworkManager.conf Using ubuntu 16.04, /etc/network/interfaces only managed lo, and [ifupdown] section of NetworkManager.conf had set managed=false. With these same settings, after upgrading to ubuntu 16.10, eth0 appears as unmanaged in nm-applet. If I modify /etc/network/interfaces and add auto eth0 iface eth0 inet dhcp And set managed=true in NetworkManager.conf [ifupdown] section, eth0 is still unmanaged despite it does get an IP from DHCP server. This is happening in my five computers (two laptops and three desktops). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1658921/+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
