No wireless networks visible on resume from suspend. Erroneous Wired connection icon in nm-applet

[Alan Pope 🍺🐧🐱 🦄]

As others have reported this I just woke my Thinkpad 450 to find no network. I resolved this by manually reconnecting with "nmcli c up id <network_name>" where <network_name> was taken from the output of "nmcli c" on the same machine.

Steps to reproduce:-

This is an intermittent issue which for me happens once in a while, but not super often to be annoying. For others it appears to happen often. I suspend my laptop multiple times daily and don't see this more than once per couple of weeks, or sometimes once a month.

* Use laptop in one location on wifi
* Suspend (shut lid) laptop
* Resume (open lid) in same location (so same wifi networks nearby)

Expected behaviour:-

* Network come back up

Actual behaviour:-

* No network connectivity
* nm-applet icon shows the two arrows as if a wired connection is made
* No or few wireless erroneous wireless networks shown nearby

* Workaround 1 (reconnect from command line)

nmcli c

(lists wireless networks, look for yours in the "NAME" column, use it in command below)

nmcli c up id NAME

* Workaround 2 (restart entire network stack)

This AskUbuntu question has one solution http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-after-16-04-upgrade#761220

Further information:-

Output of nmcli m while suspending and resuming:-

alan@gort:~$ nmcli m
Connectivity is now 'none'
Networkmanager is now in the 'asleep' state
enp0s25: unmanaged
wlp3s0: unmanaged
Connectivity is now 'full'
Networkmanager is now in the 'connected (local only)' state
enp0s25: unavailable
wlp3s0: unavailable
wlp3s0: disconnected

Output of nmcli after using workaround 1 above:-

popey_2.4g_bed: connection profile changed
Connectivity is now 'none'
Networkmanager is now in the 'connecting' state
wlp3s0: connecting (configuring)
wlp3s0: using connection 'popey_2.4g_bed'
wlp3s0: connecting (getting IP configuration)
Connectivity is now 'full'
'popey_2.4g_bed' is now the primary connection
Networkmanager is now in the 'connected' state
wlp3s0: connected
popey_2.4g_bed: connection profile changed

Hardware info:-

Thinkpad T450
alan@gort:~$ lspci | grep -i net
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (3) I218-LM (rev 03)
03:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
alan@gort:~$ uptime
 05:31:54 up 2 days, 18:03, 7 users, load average: 0.34, 0.94, 1.04

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.2.2-0ubuntu0.16.04.3
ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
Uname: Linux 4.4.0-57-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Dec 31 05:38:47 2016
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-04-27 (247 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
IpRoute:
 default via 192.168.1.1 dev wlp3s0 proto static metric 600
 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown
 10.235.160.0/24 dev lxdbr0 proto kernel scope link src 10.235.160.1 linkdown
 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.95 metric 600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
 RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
 running 1.2.2 connected started full enabled enabled enabled enabled enabled

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[maxicastro (maxicastro)]

This bug affects me and happens every time I resume from suspend on my Asus K53E with Ubuntu 16.04.

Each time I display the indicator it shows a false wired connection, and I have to do service network-manager restart. It's really annoying.

[Alberto Salvia Novella (es20490446e)]

🍺🐧🐱🦄!

[Kai-Heng Feng (kaihengfeng)]

I also had this problem before.
"Networkmanager is now in the 'asleep' state" because somehow logind failed to work, which is caused by a dbus bug.

Would you like to give new dbus a try? At least I no longer have this issue after installed dbus in xenial-proposed.

[Alan Pope 🍺🐧🐱 🦄 (popey)]

I installed dbus and friends from xenial-proposed and haven't seen the issue yet, but it happens rarely. Will keep an eye on it.

[Alan Pope 🍺🐧🐱 🦄 (popey)]

Updating to latest didn't fix it. I suspended a few times and it failed approximately 20-30% of the time.

[Kai-Heng Feng (kaihengfeng)]

Is NM asleep in all those failed cases?

[Ragnar Dunbar (zaroff)]

This persistent bug appears every first or second time after I resume from suspend. I tried Ubuntu 16.04.2 on a 2013 Macbook Air, Thinkpad T61, x200, x220, HP Compaq and Dell Latitude e4200. All of them showcase this behaviour.

[Koen Roggemans (koen-roggemans)]

Same on a Dell latitude 5580 with Intel Corporation Device 24fd (rev 78)