Ubuntu
network-manager package

  1. Bug #1585863
  2. Comment #74

Comment 74 for bug 1585863

Revision history for this message
Tony Espy (awe) wrote :

@taiebot65

Thanks. I'll take a look.

Regarding this bug, it turns out that when I was testing my version of NM with the dropped 'ScanDone' patch (wifi-Signal-on-the-wifi-device...), I'd been doing so on top of the newly re-based 1.2.6, and it turns out there was an actual fix in 1.2.6 which seems to fix the bug:

https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=nm-1-2&id=b749f7d31b7e5f57f18026a14b6a444e59a488cf

This new version of NM hasn't yet been SRU'd for xenial, as version 1.2.4-0ubuntu0.16.04.1 is still in -proposed. I'll see if maybe we can expedite this landing and skip 1.2.4 altogether.

Note, I've managed to run 200 cycles of S3 on my Thinkpad without hitting the bug. This included about 25 cycles of manual suspend/resume, and 175 iterations using fwts.