Seems to me that if NM stalls due to a race condition, then restarting NM *is* a workaround, so yes, adding additional scripts to systemd is a solution, but not the "answer".
derek On Fri, Feb 3, 2017 at 1:11 AM, Tony Espy <1585...@bugs.launchpad.net> wrote: > @Kevin > > NetworkManager already has code to monitor system signals related to > suspend/resume, so no adding additional scripts to /usr/lib/systemd > /system-sleep isn't the answer. > > @Dan > > Different bug... this bug is caused by NetworkManager's WiFi scanning > logic stalling due to a race condition. You can tell this by running > 'sudo wpa_cli' and watching for scan events. If you don't see any, then > you've hit the bug. > > I've also unfortunately confirmed that dropping the original patch from > 1.2.6 doesn't fix the problem either. I tried a cycle of 100 with my > version of 1.2.6 with the original ScanDone patch dropped and I still > tripped the bug. > > -- > 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/oem-priority/+bug/1585863/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. 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/oem-priority/+bug/1585863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs