Comment 71 for bug 1585863

I've reproduced this on a Thinkpad 410s running 16.04 LTS. The version of network-manager I used is the latest from xenial-updates: 1.2.2-0ubuntu0.16.04.3.

A few comments:

1) The fwts s3 test uses a low-level API to exercise suspend/resume. I've been working with the fwts maintainer on an extension to fwts that allows it to call out to a hook script on each iteration. This makes it possible to ensure that scanning is active for each iteration.

2) I've done some preliminary testing of the version of NM in xenial-proposed (1.2.4-0ubuntu0.16.04.1), and although it looked promising at first, I was still able to reproduce the bug.

3) We're pretty sure we know which patch [1] caused the issue, and are working to determine the best way to fix it. The fix provided in comment #5 appears to resolve it, but unfortunately it breaks the original patch's behavior.

@taiebot65

It sounds like you're hitting a different problem, so it'd probably be best if you filed a new bug.

[1] wifi-Signal-on-the-wifi-device-when-its-supplicant-i.patch