apport information ** Tags added: apport-collected xenial
** Description changed: Running Xenial on a Macbook Air. This was running Wily and was upgraded to Xenial using do-release-upgrade. Network Manager works, and can manage NICs, WiFI and VPNs that I have configured, however, the service no longer starts on boot like it did under Wily and like it should by default in any case. I have to manually start NetworkManager after each reboot using "service NetworkManager start". After that step, network is restored and works as it should. + --- + ApportVersion: 2.20.1-0ubuntu2 + Architecture: amd64 + CurrentDesktop: Unity + DistroRelease: Ubuntu 16.04 + IfupdownConfig: + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback + InstallationDate: Installed on 2015-10-21 (189 days ago) + InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020) + NetworkManager.state: + [main] + NetworkingEnabled=true + WirelessEnabled=true + WWANEnabled=true + WimaxEnabled=true + NonfreeKernelModules: wl + Package: network-manager 1.1.93-0ubuntu4 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 + Tags: xenial + Uname: Linux 4.4.0-21-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1576364/+attachment/4650568/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1576364 Title: NetworkManager service stops starting on boot after upgrade to Xenial Status in network-manager package in Ubuntu: New Bug description: Running Xenial on a Macbook Air. This was running Wily and was upgraded to Xenial using do-release-upgrade. Network Manager works, and can manage NICs, WiFI and VPNs that I have configured, however, the service no longer starts on boot like it did under Wily and like it should by default in any case. I have to manually start NetworkManager after each reboot using "service NetworkManager start". After that step, network is restored and works as it should. --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-10-21 (189 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true NonfreeKernelModules: wl Package: network-manager 1.1.93-0ubuntu4 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Tags: xenial Uname: Linux 4.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo _MarkForUpload: True nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576364/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp