This issue has been fixed by the following four commits. >From 1b925c0028cdaaf14d4ebd1f07848ba5640915c6 Mon Sep 17 00:00:00 2001 From: Tony Espy <e...@canonical.com> Date: Thu, 16 Jun 2016 15:07:33 -0400 Subject: [PATCH] wifi: clear WiFi requested_scan if suppl exits
It's possible for wpa_supplicant to exit with an outstanding requested_scan pending. This can lead to a stall condition where scanning no longer occurs. https://mail.gnome.org/archives/networkmanager-list/2016-June/msg00117.html (cherry picked from commit 899d7e5cb1eb3bddaf92de3644c49c9f634b675e) --- >From eed8fd2e43d244caa856d9993e750ff19ba62fd7 Mon Sep 17 00:00:00 2001 > > From: Tony Espy <e...@canonical.com> Date: Thu, 16 Jun 2016 15:07:32 -0400 Subject: [PATCH] wifi: clear WiFi requested_scan if suppl goes INACTIVE It's possible for wpa_supplicant to transition to INACTIVE state with an outstanding requested_scan pending. This can lead to a stall condition where scanning no longer occurs. [thal...@redhat.com: added break statement to avoid fall-through] https://mail.gnome.org/archives/networkmanager-list/2016-June/msg00116.html --- >From 788583d9fd35f9a83c932c5fa6ca059e19fcd7c6 Mon Sep 17 00:00:00 2001 > > From: Thomas Haller <thal...@redhat.com> Date: Wed, 6 Jul 2016 09:30:46 +0200 Subject: [PATCH] wifi: fix missing pending-action-remove for "scan" <warn> [1467730406.7343] device (wlp3s0): add_pending_action (2): scan already pending file devices/nm-device.c: line 10443 (nm_device_add_pending_action): should not be reached Fixes: eed8fd2e43d244caa856d9993e750ff19ba62fd7 --- >From f270bc34b4e503d5ba79d6aad1129fb4f49fee05 Mon Sep 17 00:00:00 2001 > > From: Thomas Haller <thal...@redhat.com> Date: Tue, 14 Feb 2017 15:10:36 +0100 Subject: [PATCH] device/wifi: block autoconnect while scanning is in progress We should only start autoconnecting after the scan is complete. Otherwise, we might activate a shared connection or pick a connection based on an incomplete scan list. https://bugzilla.gnome.org/show_bug.cgi?id=770938 (cherry picked from commit 2ab2254dd7336b9b7baa03ea1eb1f1c72f7ab6a8) --- ** Bug watch added: GNOME Bug Tracker #770938 https://bugzilla.gnome.org/show_bug.cgi?id=770938 ** Patch added: "network-manager_1.2.4-0ubuntu0.16.04.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1585863/+attachment/4823281/+files/network-manager_1.2.4-0ubuntu0.16.04.2.debdiff -- You received this bug notification because you are a member of Desktop 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 OEM Priority Project: Triaged Status in OEM Priority Project xenial series: Triaged Status in network-manager package in Ubuntu: Confirmed Bug description: HOW TO REPRODUCE: 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 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. WORKAROUND: (http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-after-16-04-upgrade) SYSTEM INFO: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1585863/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
