Comment 41 for bug 1585863

We used to have this. I'm sure, a decade ago, I could actually tell
whatever was managing the hibernate/suspend, in the gui, to remove certain
kernel modules on suspend and load them on resume. Now we're right back to
needing it.

derek

On Thu, Nov 17, 2016 at 1:59 PM, Hans Deragon <email address hidden> wrote:

> This serious issue is dragging to long. People want computers that
> "just work". If pinpointing the source of the problem is difficult and
> few resources are available, why not package a workaround that restarts
> NetworkManager upon resume?
>
> Attached is my workaround. Works nicely. Finally, I have a computer
> that "just works" and it's not a Mac (well, I have other issues but this
> one is solved).
>
> Simple move the script under /lib/systemd/system-sleep and ensure it is
> executable.
>
> ** Attachment added: "Workaround that restarts the NetworkManager upon
> resume."
> https://bugs.launchpad.net/ubuntu/+source/network-
> manager/+bug/1585863/+attachment/4778652/+files/
> NetworkManagerRestartWorkaroundForBug1380480.sh
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1448555).
> https://bugs.launchpad.net/bugs/1585863
>
> Title:
> WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
> required to fix it.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/network-manager/+bug/1585863/+subscriptions
>