Re: Issues resuming from hibernation

[solitone <solitone@mail.com>]

On Saturday, December 24, 2016 6:28:22 AM CET solitone wrote:
> I confirm the problem has indeed to do with hibernation (suspending to disk). 

Specifically, here's the output of nmcli after either a cold startup or 
resuming from RAM:
#####
solitone@alan:~$ nmcli
wlp3s0: connected to colossus
        "Broadcom Limited BCM43602 802.11ac Wireless LAN SoC"
        wifi (brcmfmac), 98:01:A7:9D:0F:BD, hw
        ip4 default
        inet4 192.168.0.30/24
        inet6 fe80::9a01:a7ff:fe9d:fbd/64

lo: unmanaged
        loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
[...]
#####

Immediately after resuming from hibernation, here's what I got instead:
#####
solitone@alan:~$ nmcli

(process:2536): nmcli-CRITICAL **: Error: Could not create NMClient object: 
Timeout was reached.
#####

After a couple of minutes I repeated the command, and got:
#####
solitone@alan:~$ nmcli
wlp3s0: disconnected
        "Broadcom Limited BCM43602 802.11ac Wireless LAN SoC"
        wifi (brcmfmac), 98:01:A7:9D:0F:BD, hw, mtu 1500

lo: unmanaged
        loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
[...]
#####

I tried to manually reconnect the device, but it didn't work:
#####
solitone@alan:~$ nmcli device connect wlp3s0
Error: Failed to add/activate new connection: A 'wireless' setting is required 
if no AP path was given.
#####