Hi @cascagrossa, just to clarify: my impression is that in order to trigger the bug you'll need to suspend somewhere where the WLAN network you want to connect to at resume time isn't available as it's the scan aspect of things that appears to be inhibited. This is evidenced by the fact that he network-mgr UI shows a stale list of WiFi networks when the bug manifests itself; I've don't *think* I've ever had this bug affect me in a stationary suspend/resume scenario.
-- 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
