Comment 22 for bug 1585863

Bug# 1455097 "/etc/pm/sleep.d/ is no more processed" confirms that any solution involving "/etc/pm/sleep.d/" will not work since systemd took over. auspex solution works (thank you), although in my case, I simply restart the Network Manager (systemctl restart network-manager) to be really sure that Wifi will come up (see below).

That said, this bug is a shame to Ubuntu. Any consumer expects wifi/networking to come up upon resume. It is basic. Nobody at Canonical suffers from this problem?

If it is too hard to find a solution at the heart of the problem in a timely matter, we should quickly make a patch to force a rescan or restart the Network Manager. Who on this bug list is entitled to take a decision and package a script under '/lib/systemd/system-sleep'? Anyone? What is the process to get things done?

Following is the reason why I prefer a restart of the Network Manager. There were times that the Network Manager (at least in 14.04 for sure, 16.04, not so sure) would not even come out from sleep. This is why I prefer to restart it upon resume; it fixes multiple problems such as coming out of sleep and Wifi scanning. It does not cost much and I do not find any downsides, except for the nm-applet disappearing and reappearing quickly upon resume.