I can confirm that after every resume my wifi is not working. I used to "solve" it by network-manager restart but running "wpa_cli resume" manually fixes the problem as well.
I tried the sleep workaround by Hans but it did not help. I can see this in /var/log/syslog: Jan 19 00:20:34 vaclav-ntb systemd[1]: Reached target Sleep. Jan 19 00:20:34 vaclav-ntb systemd[1]: Starting Suspend... Jan 19 00:20:34 vaclav-ntb systemd-sleep[6171]: Failed to connect to non-global ctrl_ifname: (nil) error: No such file or directory Jan 19 00:20:34 vaclav-ntb systemd-sleep[6173]: /lib/systemd/system-sleep/wpasupplicant failed with error code 255. Jan 19 00:20:34 vaclav-ntb systemd-sleep[6171]: Suspending system... [snip] Jan 19 00:20:57 vaclav-ntb NetworkManager[3609]: <info> [1484781657.4625] manager: waking up... Jan 19 00:20:57 vaclav-ntb NetworkManager[3609]: <info> [1484781657.4626] device (wlan0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2] ... Jan 19 00:20:57 vaclav-ntb NetworkManager[3609]: <info> [1484781657.8564] manager: NetworkManager state is now CONNECTED_LOCAL Jan 19 00:20:57 vaclav-ntb wpa_supplicant[1606]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none Jan 19 00:20:57 vaclav-ntb wpa_supplicant[1606]: dbus: Failed to construct signal Jan 19 00:20:57 vaclav-ntb NetworkManager[3609]: <info> [1484781657.9052] device (wlan0): supplicant interface state: starting -> ready Jan 19 00:20:57 vaclav-ntb NetworkManager[3609]: <info> [1484781657.9053] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42] Jan 19 00:20:57 vaclav-ntb kernel: [138425.339676] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready -- 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/1585863 Title: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it. Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in network-manager package in Ubuntu: Confirmed Bug description: Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 Packages: libnm-glib-vpn1:amd64 1.2.2-0ubuntu2 libnm-glib4:amd64 1.2.2-0ubuntu2 libnm-util2:amd64 1.2.2-0ubuntu2 libnm0:amd64 1.2.2-0ubuntu2 network-manager 1.2.2-0ubuntu2 Reproduce steps: 1. Install fwts by `sudo apt-get install fwts`. 2. Run the suspend & resume stress test. sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 --s3-delay-delta=5 Expected result: The WiFi still functioned. Actual result: The WiFi can not connect to any access point and we have to execute `sudo wpa_cli scan` manually to make it work again. P.S. Ubuntu 16.04 also has the same issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1585863/+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
