[Touch-packages] [Bug 1574347] Re: [SRU] Re-read the link type if the name changed
larabi: I came from Fedora, and I had been running it for the last releases on my laptop. Never had any WiFi issues, so there's not anything wrong with my hardware. I recently installed Ubuntu 16.04.1 LTS, but these WiFi issues are quite annoying and I'm contemplating switching back to Fedora. I don't understand how this still hasn't been fixed in an LTS version of the OS. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1574347 Title: [SRU] Re-read the link type if the name changed Status in NetworkManager: Fix Released Status in OEM Priority Project: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Released Bug description: [Impact] NM needs to re-read the DEVTYPE after the device name changed, an example is that WiFi network list disappears from network manager applet [Testcase] 1. Boot the system. It should include a wireless device. 2. In a terminal, run 'nmcli dev'. 3. In the correct case, the line for the wireless device should read "wifi" under the TYPE column. In a failure case, it will read "ethernet". After upgrading to the new version, the repeating the above steps should give expected behavior. [Regression Potential] Potential of causing regression is relatively small for a one line change to re-read a value to be known. --- Problems:- 1. The network manager applet does not show the list of WiFI APs it can find. 2. The network manager applet does not the name of the AP to which it is connected 3. The icon of the applet shows two vertical arrows in opposite direction - the wired connection symbol and NOT the wifi connected icon. Temporary Workaround:- Log out and again log back in. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1574347/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
This bug seems to affect a lot of people on Ask Ubuntu too: "Wifi doesn't work after suspend after 16.04 upgrade" http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend- after-16-04-upgrade, including me. I have a Thinkpad T440 where I previously ran Fedora for multiple releases. Never had any issues with the wifi in combination with sleep/resume. The other day I installed Ubuntu 16.04.1 and ran an update. The workaround on Ask Ubuntu that is to run `sudo systemctl restart network-manager.service` works for me, but I feel this shouldn't be an issue in the first place after the first service pack on an LTS release. -- You received this bug notification because you are a member of Ubuntu Touch seeded 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: New Status in OEM Priority Project xenial series: New Status in network-manager package in Ubuntu: Confirmed Bug description: 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:amd641.2.2-0ubuntu2 network-manager 1.2.2-0ubuntu2 Reproduce steps: 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 Expected result: The WiFi still functioned. Actual 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. P.S. Ubuntu 16.04 also has the same issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1585863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
