NM doesn't scan for wifi networks after suspend

[Julia Palandri]

Sometimes, after waking up the laptop from hibernation, nm-applet won't scan for networks. In these cases, the list of available Wifis can be just outdated or directly empty.

Switching Wireless on/off and Network on/off doesn't trigger a scan.

Usually running sudo iwlist <interface> scan on a terminal makes the wifi networks available immediately in nm-applet

I'm using 16.04 (ubt had the same problem on 15.10)
network-manager-gnome:
  Installed: 1.2.0-0ubuntu0.16.04.4

[Launchpad Janitor (janitor)]

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

[Julia Palandri (julia-palandri)]

Today I saw it again and scanning on the terminal didn't work. Tried with "nmcli d wifi list" which showed the networks available on the terminal, but not on the applet. In the end, I added the new network by hand, which worked and got me connected, but it was annoying. I then turned on a hotspot my computer knew, and it got connected right away - could it be that it's not *displaying* the networks, but it does scan them?

[Martin Pitt (pitti)]

Do you mean "suspend" instead of "hibernate"? Could be a duplicate of bug 1585863.

[Julia Palandri (julia-palandri)]

OOps, yes. I meant suspend, indeed. I will try with that method to see if that works for me, but as per #2 i can have a hard time trying to fix it

[Matteo Dell'Amico (della)]

I have the same problem, I'm able to get NM connect to the wifi network by running either of "sudo wpa_cli scan" and "sudo iwlist <interface> scan". With respect to what happens on my computer, the behavior is the same described in bug 1585863.