I'm surprised this is still a thing. I added the common systemd "restart network-manager on resume" script most folks with this issue have used. I added it quite a while ago. My system has been working consistently since then without issue... to the point I actually forgot that this bug existed.
I understand the burning desire to fix the problem at hand, but months (soon to be a year) later, this issue still exists. I don't see the trade-off/downsides/consequences with this work-around being applied. If a downside does exist, I haven't seen it, but what I have seen is the benefit of it being in place as it circumvents this issue entirely. Sorry - I just don't see the point of this bug trailing on longer and longer while users unaware of the "restart network-manager on resume" fix continue to deal with the headache, while on the other hand, had that work-around been issued, folks wouldn't be as angry about this issue as they clearly are. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1585863 Title: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it. Status in NetworkManager: New Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in network-manager package in Ubuntu: Confirmed Bug description: Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 Packages: libnm-glib-vpn1:amd64 1.2.2-0ubuntu2 libnm-glib4:amd64 1.2.2-0ubuntu2 libnm-util2:amd64 1.2.2-0ubuntu2 libnm0:amd64 1.2.2-0ubuntu2 network-manager 1.2.2-0ubuntu2 Reproduce steps: 1. Install fwts by `sudo apt-get install fwts`. 2. Run the suspend & resume stress test. sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 --s3-delay-delta=5 Expected result: The WiFi still functioned. Actual result: The WiFi can not connect to any access point and we have to execute `sudo wpa_cli scan` manually to make it work again. P.S. Ubuntu 16.04 also has the same issue. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1585863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
