Comment 62 for bug 1585863

Revision history for this message
Vaclav Rehak (vaclav-n) wrote :

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