I just upgraded network-manager to test your workaround but I cannot reproduce this bug anymore. I tried to restart networking and the network-manager services. I also tried to purge network-manager and reinstall it again. I didn't try to reboot.
The bug might affect new installations only. Maybe network-manager remembers which devices it has already managed and keeps managing them? Or the previous version of network-manager creates configuration files that makes the new version work correctly? Still, cat /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf effectively gives me: [keyfile] unmanaged-devices=*,except:type:wifi,except:type:wwan I don't know if this file was present when I was using the previous version of network-manager. The new version of network-manager works correctly with this file so it seems there is something else involved. Le 03/11/2016 à 17:05, 林博仁 a écrit : > Update Workaround in #2, in fact you need to remove > /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf instead. > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638842 Title: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
