Thanks for the log. Putting the interesting excerpt here for convenience: Mar 09 23:27:59 fry NetworkManager[1000]: <info> (wlan0): device state change: secondaries -> activated (reason 'none') [90 100 0] Mar 09 23:27:59 fry NetworkManager[1000]: <info> NetworkManager state is now CONNECTED_LOCAL Mar 09 23:27:59 fry NetworkManager[1000]: <info> NetworkManager state is now CONNECTED_GLOBAL [...] Mar 10 00:37:20 fry NetworkManager[1000]: <info> sleep requested (sleeping: no enabled: yes) Mar 10 00:37:20 fry NetworkManager[1000]: <info> sleeping... Mar 10 10:04:24 fry NetworkManager[1000]: <info> waking up... Mar 10 10:04:24 fry NetworkManager[1000]: <info> (wlan0): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37] Mar 10 10:04:24 fry NetworkManager[1000]: <info> (wlan0): deactivating device (reason 'sleeping') [37]
So it seems that the "activated -> unmanaged" action should be done *before* "sleeping...", and then it just forgets to bring it back up after waking up. Here it has the correct order, so that sounds like a race condition. This part (logind interaction) hasn't actually changed in quite some time. Out of interest, do you get this error under upstart too? This doesn't actually sound specific to using systemd as init, but it would be nice to confirm that. Otherwise it's another data point for debugging this. Thanks! -- 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/1422143 Title: No wifi connection after suspend with systemd Status in One Hundred Papercuts: Confirmed Status in network-manager package in Ubuntu: Incomplete Bug description: Using systemd as my default init system if I resume from suspend my laptop, it doesn't automatically reconnect to the wireless network and it doesn't list the available network connections. The only way to get a wireless connection is to restart the network- manager daemon or going to the gnome-control-center, disable wireless and enable it again. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu6 Uname: Linux 3.19.0-031900-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 Date: Sun Feb 15 18:27:39 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-10-22 (116 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) IpRoute: default via 10.0.0.1 dev wlan0 proto static metric 1024 10.0.0.0/24 dev wlan0 proto kernel scope link src 10.0.0.36 169.254.0.0/16 dev wlan0 scope link metric 1000 SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-01-13 (32 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/2 openhost_caldas 09d1f69d-d3da-4978-a69c-d94455db7ecf /org/freedesktop/NetworkManager/ActiveConnection/0 docker0 bridge unavailable /org/freedesktop/NetworkManager/Devices/3 -- -- -- eth0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- -- 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/hundredpapercuts/+bug/1422143/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
