GNOME Bugzilla – Bug 765831
Wifi fails to resume from standby
Last modified: 2016-09-05 07:40:24 UTC
System fails to detect any Wifi network SSID's on resume from standby sudo service network-manager restart brings the list of wireless network back in operation and you can continue as normal until next standby. Or a full system restart. Wireless card replaced with another working model. System fully patched as of 28.04.2016 description: Wireless interface product: Wireless 7260 vendor: Intel Corporation physical id: 0 bus info: pci@0000:02:00.0 logical name: wlp2s0 version: 73 serial: 0c:8b:fd:b5:7c:0f width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=4.4.0-21-generic firmware=16.242414.0 ip=10.10.10.239 latency=0 link=yes multicast=yes wireless=IEEE 802.11abgn resources: irq:47 memory:f7a00000-f7a01fff Description: Ubuntu 16.04 LTS Release: 16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 28 17:17:33 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-15 (13 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) IpRoute: default via 10.10.10.1 dev wlp2s0 proto static metric 600 10.10.10.0/23 dev wlp2s0 proto kernel scope link src 10.10.10.239 metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. Tags: xenial amd64 apport-bug Edit Tag help Alex (alexeffemey-9) wrote on 2016-04-28: #1 CRDA.txt Edit (227 bytes, text/plain; charset="utf-8") Dependencies.txt Edit (8.4 KiB, text/plain; charset="utf-8") IpAddr.txt Edit (833 bytes, text/plain; charset="utf-8") IwConfig.txt Edit (510 bytes, text/plain; charset="utf-8") JournalErrors.txt Edit (49.7 KiB, text/plain; charset="utf-8") NetDevice.eno1.txt Edit (861 bytes, text/plain; charset="utf-8") NetDevice.lo.txt Edit (248 bytes, text/plain; charset="utf-8") NetDevice.wlp2s0.txt Edit (920 bytes, text/plain; charset="utf-8") NetworkManager.conf.txt Edit (75 bytes, text/plain; charset="utf-8") PciNetwork.txt Edit (1.3 KiB, text/plain; charset="utf-8") RfKill.txt Edit (176 bytes, text/plain; charset="utf-8") WifiSyslog.txt Edit (165.7 KiB, text/plain; charset="utf-8") nmcli-con.txt Edit (1.1 KiB, text/plain; charset="utf-8") nmcli-dev.txt Edit (1015 bytes, text/plain; charset="utf-8") Hide Alex (alexeffemey-9) wrote on 2016-04-28: #2 Dell Latitude E5540 tested system76 bonobo extreme (will submit wifi card info once home) Hide Sebastien Bacher (seb128) wrote 8 hours ago: #3 Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.
Please attach NetworkManager's logfile with DEBUG-logging enabled. For that, edit /etc/NetworkManager/NetworkManager.conf to have [logging] level=TRACE Restart NM, reproduce the issue, and attach the logfile (from `journalctl -u NetworkManager`). thank you.
From the logfile on launchpad, it seems that after wlp2s0 successfully connected after resume. What exactly is the problem? That the scanlist was empty? What gives `nmcli device wifi`? Does `nmcli device wifi rescan` help?
Created attachment 327070 [details] Network Manager log requested Network manager log generated while troubleshooting Please attach NetworkManager's logfile with DEBUG-logging enabled. For that, edit /etc/NetworkManager/NetworkManager.conf to have [logging] level=TRACE Restart NM, reproduce the issue, and attach the logfile (from `journalctl -u NetworkManager`).
Further investigation shows a fresh boot displays wireless SSID's via gui or command for network manager within Ubuntu 16.04, you can list a list of all wifi networks in the area. When going into standby then resuming the icon changes from Wifi symbol to that of an Ethernet connection and fails to display any wifi networks or connect to the original SSID. When running sudo service NetworkManager restart this resumes normal NetworkManager operation and the Wifi reconnects. Place the system into standby again and resume and the Wifi still operates. Reboot and again place the system into standby and resume the connection fails and no SSID networks are found.
* SSID MODE CHAN RATE SIGNAL BARS SECURITY -- Infra 40 0 Mbit/s 82 ▂▄▆█ WEP * Lovepuff Infra 44 54 Mbit/s 54 ▂▄__ WPA2 Lovepuff Infra 6 54 Mbit/s 45 ▂▄__ WPA2 BTWifi-X Infra 1 54 Mbit/s 44 ▂▄__ WPA1 WPA2 802.1X BTHub5-FXKF Infra 1 54 Mbit/s 37 ▂▄__ WPA2 BTWifi-with-FON Infra 1 54 Mbit/s 35 ▂▄__ TALKTALKB93E7A Infra 8 54 Mbit/s 35 ▂▄__ WPA1 WPA2 SKYDA398 Infra 1 54 Mbit/s 29 ▂___ WPA2 TALKTALKB93E7A Infra 36 54 Mbit/s 22 ▂___ WPA1 WPA2 EE-BrightBox-mfrn44 Infra 1 54 Mbit/s 20 ▂___ WPA1 WPA2 BTWifi-X Infra 6 54 Mbit/s 20 ▂___ WPA1 WPA2 802.1X TillyTillyTilly Infra 6 54 Mbit/s 20 ▂___ WPA2 BTWifi-with-FON Infra 6 54 Mbit/s 20 ▂___ BTHub5-5J73 Infra 1 54 Mbit/s 19 ▂___ WPA2 BTWifi-with-FON Infra 1 54 Mbit/s 19 ▂___ BTHub4-N8KG Infra 6 54 Mbit/s 19 ▂___ WPA1 WPA2 BTWifi-X Infra 1 54 Mbit/s 17 ▂___ WPA1 WPA2 802.1X under normal operation
nmcli device wifi rescan fails to detect any wifi on resume from failure, only sudo service NetworkManager restart reconnects
(In reply to Alex from comment #4) > When going into standby then resuming the icon changes from Wifi symbol to > that of an Ethernet connection This is probably be a duplicate of bug 764803
I'd like to second the above bug report. Running on a ThinkPad T430, started experiencing this issue only after upgrading to Ubuntu 16.04. After wakeup from suspend, Network Manager does not display a list of wifi networks, and doing systemctl restart network-manager.service brings things back to normal. This seems different from bug 764803 because there it's intermittent and happens on boot, while for me this is consistent and happens only on wakeup.
I agree I don't think it matches Bug 764803 The Wifi does work on cold boot until you standby then resume then the problem seems to occur. However after restarting the network-manager and then standby and resume it works over and over until the next cold boot, tested with Dell Latitude E6400 E5520 E5540 and System76 Bonobo extreme (Various Wifi cards) seems to affect Ubuntu 16.04 not 14.04.
Hi Alex, the logfile from commit 3 does not show the issue (it shows only the second when NetworkManager starts). could you please attach a complete logfile, including the suspend/resume part? Thank you.
Update on my comment #8: The bug has gone away and I am no longer able to reproduce it. I am guessing that I auto-installed an update that has fixed it.
Woops sorry only just spotted the update i wilk try my updates this evening see if it vanishes.
This seems fixed according to comment 11, please reopen if needed.