>Can you replicate the network manager failure when upgrading in a more normal manner?
Using do-release-upgrade *IS* a normal manner, and it is working as intended. Before Gutsy was released, it was even the _recommended_ method of upgrading in several situations. The same behavior happened to me six months ago when upgrading from Feisty to Gutsy using adept, so I'm marking this as confirmed. This is really a bug in NetworkManager, which hijacks the network configuration without telling the user. The behavior was documented back when Gutsy was released (https://wiki.ubuntu.com/GutsyGibbon/ReleaseNotes), but no one bothered to fix the problem in the intervening six months. The best work-around that has worked for me is to uninstall dhcdbd and network-manager before upgrading. If, after you do the upgrade, you want Network Manager to manage your network configuration, you can always add it back. I've never missed Network Manager, and none of my customers have either, so you may decide just to leave it out. If you want a GUI interface for managing your network, network-config does a better job IMHO. ** Changed in: update-manager-core (Ubuntu) Status: Incomplete => Confirmed -- do-release-upgrade to gutsy disables eth0 https://bugs.launchpad.net/bugs/151169 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
