Hello Brian, or anyone else affected, Accepted network-manager into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/network- manager/1.2.6-0ubuntu1.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Description changed: Impact ------ When upgrading from Xenial (with all updates installed) to Yakkety you will boot to a system without networking - sad! Test Case --------- 1) Boot a xenial desktop system 2) Ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is installed 3) Upgrade to yakkety 4) Reboot 5) Observe you have no network - If you install the version of network-manager from -proposed before - rebooting you should have a network connection after you reboot. - + If you install the version of network-manager from yakkety-proposed + before rebooting you should have a network connection after you reboot. Regression Potential -------------------- Any failure to manage ethernet or wireless devices after upgrade, or issues with the use of netplan in conjunction with NetworkManager should be investigated as potential regressions. For example, if after upgrading, ethernet devices are no longer managed, or if devices that should be explicitly ignored by NetworkManager due to existing user configuration are now managed, these would indicate a possible regression caused by this update. - Original Description -------------------- nplan was installed during the upgrade process but I had no network connectivity after upgrading. Apparently, no package wanted to manage my ethernet connection. ProblemType: BugDistroRelease: Ubuntu 16.10 Package: ubuntu-release-upgrader-core 1:16.10.10 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Mon Mar 27 11:34:04 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2013-01-16 (1531 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116) PackageArchitecture: allSourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to yakkety on 2017-03-17 (10 days ago) VarLogDistupgradeTermlog: modified.conffile..etc.update-manager.meta-release: [modified] mtime.conffile..etc.update-manager.meta-release: 2013-10-08T06:39:09.818913 ** Changed in: network-manager (Ubuntu Yakkety) Status: Triaged => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1676547 Title: No network connectivity after upgrade from 16.04 to 16.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1676547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
