Ah, I'm on upstart now and it's still happening. I think for me this started around the time the new NM upstream release was uploaded, so I'd start investigating what changed there. Even if it did happen sometimes before (e.g. if bug #1270257 is a dupe), it seems way more frequent now. I personally never had this issue up until quite recently.
-- 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/1422096 Title: Occasionally no network on resume Status in network-manager package in Ubuntu: New Bug description: Sometimes I resume and n-m thinks that lxcbr0 is a connected wired network, so doesn't connect to the wireless network that I actually want to use until I restart it. laney@iota> nmcli d DEVICE TYPE STATE CONNECTION lxcbr0 bridge connected lxcbr0 virbr0 bridge connected virbr0 50:46:5D:18:E7:06 bt disconnected -- wlan0 wifi disconnected -- eth0 ethernet unavailable -- lo loopback unmanaged -- virbr0-nic tap unmanaged -- laney@iota> nmcli d w l ifname wlan0 * SSID MODE CHAN RATE SIGNAL BARS SECURITY laney@iota> cat /etc/network/interfaces auto lo iface lo inet loopback ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu6 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Feb 15 10:37:28 2015 IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2012-10-18 (850 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) IpRoute: default via 192.168.1.1 dev wlan0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.134 SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2014-07-30 (200 days ago) 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/1422096/+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
