I'm facing the same bug while running 16.04 on a Dell Vostro 3558 (iwlwifi).
I edited the file /lib/systemd/system-sleep/wpasupplicant and changed the bit that goes '/sbin/wpa_cli resume ;;' to 'systemctl restart network-manager.service ;;'. Now when I resume from suspend, at first the network is disabled but in a few seconds, network manager restarts and my wi-fi connection reconnects. The logs confirm this: Apr 24 13:58:04 prashant-Vostro-3558 NetworkManager[806]: <info> [1461486484.8054] manager: sleep requested (sleeping: no enabled: yes) Apr 24 13:58:04 prashant-Vostro-3558 NetworkManager[806]: <info> [1461486484.8055] manager: sleeping... Apr 24 13:58:04 prashant-Vostro-3558 NetworkManager[806]: <info> [1461486484.8056] device (wlp6s0): state change: activated -> unmanaged (reason 'sle Apr 24 13:58:04 prashant-Vostro-3558 NetworkManager[806]: <info> [1461486484.8176] dhcp4 (wlp6s0): canceled DHCP transaction, DHCP client pid 2045 Apr 24 13:58:04 prashant-Vostro-3558 NetworkManager[806]: <info> [1461486484.8176] dhcp4 (wlp6s0): state changed bound -> done Apr 24 13:58:04 prashant-Vostro-3558 NetworkManager[806]: <info> [1461486484.8295] dns-mgr: Writing DNS information to /sbin/resolvconf Apr 24 13:58:04 prashant-Vostro-3558 dnsmasq[2152]: setting upstream servers from DBus Apr 24 13:58:04 prashant-Vostro-3558 NetworkManager[806]: <info> [1461486484.8405] manager: NetworkManager state is now ASLEEP Apr 24 15:45:56 prashant-Vostro-3558 NetworkManager[806]: <info> [1461492956.5797] manager: WiFi now disabled by radio killswitch Apr 24 15:45:56 prashant-Vostro-3558 systemd[1]: Stopping Network Manager... Apr 24 15:45:56 prashant-Vostro-3558 NetworkManager[806]: <info> [1461492956.6291] caught SIGTERM, shutting down normally. Apr 24 15:45:56 prashant-Vostro-3558 NetworkManager[806]: <info> [1461492956.6301] device (enp7s0): state change: unavailable -> unmanaged (reason 'u Apr 24 15:45:56 prashant-Vostro-3558 NetworkManager[806]: <info> [1461492956.6542] exiting (success) Apr 24 15:45:56 prashant-Vostro-3558 systemd[1]: Stopped Network Manager. Apr 24 15:45:56 prashant-Vostro-3558 systemd[1]: Starting Network Manager... Apr 24 15:45:56 prashant-Vostro-3558 systemd[1]: Started Network Manager. Apr 24 15:45:56 prashant-Vostro-3558 NetworkManager[6370]: <info> [1461492956.7194] NetworkManager (version 1.1.93) is starting... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1422143 Title: No wifi connection after suspend with systemd due to missing "wpa_cli suspend" Status in One Hundred Papercuts: Confirmed Status in NetworkManager: Unknown Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Wily: Fix Committed Status in wpa source package in Xenial: Fix Released 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. SRU INFORMATION =============== In some of these cases this bug can be worked around by calling "wpa_cli suspend/resume" before/after suspend, like we used to do with the old pm-utils quirks (/usr/lib/pm-utils/sleep.d/60_wpa_supplicant). This only affects particular hardware, and thus this needs to be tested by affected reporters, there is no general reproducer for arbitrary systems. 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
