Network Manager fails to reconnect to wifi after resuming from suspend

[Cerin]

After resuming from suspend on my laptop, I have wifi enabled, but Network Manager does not automatically reconnect, and it's list of available wifi networks is blank.

If I run `sudo service network-manager restart`, then this fixes everything and it automatically detects and connects to my wifi hotspot, but this shouldn't be necessary.

This problem seems specific to 16.04. Under 14.04, NM worked perfectly. After I upgraded my 14.04 install to 16.04 it started happening, however, I assumed this was likely due to some broken config file leftover from the upgrade. However, I recently did a fresh install to the same laptop on a blank hard drive, and the problem still exists.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.2.2-0ubuntu0.16.04.3
ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
Uname: Linux 4.4.0-62-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Feb 11 13:25:56 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-01-21 (20 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
 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.122 metric 600
 192.168.121.0/24 dev virbr1 proto kernel scope link src 192.168.121.1 linkdown
 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
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.