Marking as Fix Released, based on Chih's comment
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: oem-priority
Status: Incomplete => Fix Released
--
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/1578127
Title:
Sometimes WLAN detects no SSID after s3
Status in NetworkManager:
New
Status in OEM Priority Project:
Fix Released
Status in network-manager package in Ubuntu:
Fix Released
Bug description:
[Steps to reproduce]
1. Boot into OS
2. Do s3 a few times
3. Check if wifi is still working after s3
[Expected results]
wifi still working correctly after s3
[Actual results]
1. Wifi shows "disconnected" in network-manager (both in applet and from
command "nmcli d status")
2. Only one random SSID is displayed in network-manager applet, but wifi
connection cannot be established at all with this SSID. Clicking on the SSID
results in pop up window in the comment #2 below
3. "nmcli d wifi rescan" does not resolve issue
4. "iwlist [interface] scan" returns nothing and does not reolve issue
5. "nmcli d wifi connect [any SSID that you know should exist]" results in
SSID not found and does not resolve issue
6. "sudo service network-manager restart", warm boot, cold boot resolves issue
[Details]
OS: Xenial based OEM image
WLAN module: Marvel [11ab:2b38]
network-manager:
- 1.2.0-0ubuntu0.16.04.1 (fail rate 1/20~ 1/15)
- 1.1.93 (fail rate 1/15)
To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1578127/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
