cannot view wifi networks after resume from suspend

Bug #1748812 reported by Yuriy Vidineev on 2018-02-12
This bug affects 4 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)

Bug Description

On 2 laptops (Dell XPS13 9360 with ath10k and Lenovo T530 with iwlwifi) I have the same issue:
After resume from suspend nm-applet doesn't show any information about connected/available wi-fi connections. Please see screenshot in attach.
I can see current connection via CLI:

nmcli dev
docker0 bridge connected docker0
wlp58s0 wifi connected Turris
lo loopback unmanaged --

Now I have to run `killall nm-applet && nm-applet &` after every suspend. That fixes my issue

I think it's a duplicate of but I was asked to submit separate bug

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.2.6-0ubuntu0.16.04.2
Uname: Linux 4.15.0-041500rc9-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Feb 11 19:41:21 2018
 # This is a distribution channel descriptor
 # For more information see
EcryptfsInUse: Yes
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-10-06 (493 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47
 default via dev wlp58s0 proto static metric 600 dev docker0 scope link metric 1000 linkdown dev docker0 proto kernel scope link src linkdown dev wlp58s0 proto kernel scope link src metric 600
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
 docker0 bridge connected /org/freedesktop/NetworkManager/Devices/1 docker0 440d4ade-78be-45c3-a821-903971861d0c /org/freedesktop/NetworkManager/ActiveConnection/0
 wlp58s0 wifi connected /org/freedesktop/NetworkManager/Devices/3 Turris e9dddd63-362e-4e4a-ac98-54af278d348d /org/freedesktop/NetworkManager/ActiveConnection/88
 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- --
 running 1.2.6 connected started full enabled enabled enabled enabled enabled

Yuriy Vidineev (adeptg) wrote :
Yuriy Vidineev (adeptg) wrote :

Here is how nm-applet looks after restart (killall nm-applet && nm-applet &)

Shih-Yuan Lee (fourdollars) wrote :

`Uname: Linux 4.15.0-041500rc9-generic x86_64` is not the kernel that Ubuntu supported.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in network-manager (Ubuntu):
status: New → Confirmed
Kai-Heng Feng (kaihengfeng) wrote :

So what does it look like before restart?

GrzesiekC (grzesiekc) wrote :

The same here:

Linux E7470 4.13.0-33-generic #36~16.04.1-Ubuntu SMP Wed Feb 7 23:32:33 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Yuriy Vidineev (adeptg) wrote :

Shih-Yuan Lee,

> `Uname: Linux 4.15.0-041500rc9-generic x86_64` is not the kernel that Ubuntu supported.

I have this bug on a wide range of kernels from 4.4 to 4.15 We completely the same behaviour. On 2 laptops with different wi-fi adapters (ath10k and iwlwifi kernel modules)

Here is complete list of installed kernel versions and on every kernel I have this bug.

linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1
linux-image-4.10.0-33-generic 4.10.0-33.37~16.04.1
linux-image-4.10.0-35-generic 4.10.0-35.39~16.04.1
linux-image-4.10.0-37-generic 4.10.0-37.41~16.04.1
linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1
linux-image-4.10.0-40-generic 4.10.0-40.44~16.04.1
linux-image-4.10.0-42-generic 4.10.0-42.46~16.04.1
linux-image-4.13.0-26-generic 4.13.0-26.29~16.04.2
linux-image-4.13.0-31-generic 4.13.0-31.34~16.04.1
linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1
linux-image-4.13.11-041311-generic 4.13.11-041311.201711020532
linux-image-4.13.3-041303-generic 4.13.3-041303.201709200606
linux-image-4.13.4-041304-generic 4.13.4-041304.201709270931
linux-image-4.14.0-041400-generic 4.14.0-041400.201711122031
linux-image-4.14.2-041402-generic 4.14.2-041402.201711240330
linux-image-4.14.7-041407-generic 4.14.7-041407.201712171031
linux-image-4.14.8-041408-generic 4.14.8-041408.201712200555
linux-image-4.15.0-041500-generic 4.15.0-041500.201802011154
linux-image-4.15.0-041500rc9-generic 4.15.0-041500rc9.201801212130
linux-image-4.4.0-101-generic 4.4.0-101.124
linux-image-4.4.0-103-generic 4.4.0-103.126
linux-image-4.4.0-104-generic 4.4.0-104.127
linux-image-4.4.0-109-generic 4.4.0-109.132
linux-image-4.4.0-112-generic 4.4.0-112.135
linux-image-4.4.0-93-generic 4.4.0-93.116
linux-image-4.4.0-96-generic 4.4.0-96.119
linux-image-4.4.0-97-generic 4.4.0-97.120
linux-image-4.4.0-98-generic 4.4.0-98.121
linux-image-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-image-4.9.32-040932-generic 4.9.32-040932.201706141032
linux-image-extra-4.10.0-32-generic 4.10.0-32.36~16.04.1
linux-image-extra-4.10.0-33-generic 4.10.0-33.37~16.04.1
linux-image-extra-4.10.0-35-generic 4.10.0-35.39~16.04.1
linux-image-extra-4.10.0-37-generic 4.10.0-37.41~16.04.1
linux-image-extra-4.10.0-38-generic 4.10.0-38.42~16.04.1
linux-image-extra-4.10.0-40-generic 4.10.0-40.44~16.04.1
linux-image-extra-4.10.0-42-generic 4.10.0-42.46~16.04.1
linux-image-extra-4.13.0-26-generic 4.13.0-26.29~16.04.2
linux-image-extra-4.13.0-31-generic 4.13.0-31.34~16.04.1
linux-image-extra-4.13.0-32-generic 4.13.0-32.35~16.04.1
linux-image-extra-4.4.0-101-generic 4.4.0-101.124
linux-image-extra-4.4.0-103-generic 4.4.0-103.126
linux-image-extra-4.4.0-104-generic 4.4.0-104.127
linux-image-extra-4.4.0-109-generic 4.4.0-109.132
linux-image-extra-4.4.0-112-generic 4.4.0-112.135
linux-image-extra-4.4.0-93-generic 4.4.0-93.116
linux-image-extra-4.4.0-96-generic 4.4.0-96.119
linux-image-extra-4.4.0-97-generic 4.4.0-97.120
linux-image-extra-4.4.0-98-generic 4.4.0-98.121
linux-image-extra-4.8.0-58-generic 4.8.0-58.63~16.04.1

Yuriy Vidineev (adeptg) wrote :

Kai-Heng Feng, you can see screenshot before restart in original bug description:

> screenshot of nm-applet before restart

Shih-Yuan Lee (fourdollars) wrote :

It looks like it is a preloaded Ubuntu system.
Could you help to provide some logs as the followings?

`sudo mount /dev/sda2 /mnt` or `sudo mount /dev/nvme0n1p2 /mnt` and then attach /mnt/bto.xml
dpkg -l > dpkg.log and then attach dpkg.log

Yuriy Vidineev (adeptg) wrote :

Yes it's Dell XPS 13 that comes with Ubuntu 16.04 preinstalled. But I have the same issue on Lenovo T530 where I installed Ubuntu manually.

From Dell XPS 13 9360:

kakaduplum Fri, 24 Jun 2016 10:26:40 +0000

There is no /mnt/bto.xml. Here is list of files I have on /dev/nvme0n1p2:

boot casper debs dell-e-star dists efi.factory factory install installer isolinux md5sum.txt pool preseed scripts

Please find dpkg.log in attachment

Shih-Yuan Lee (fourdollars) wrote :

Could you also provide `lspci -nnk > lspci.log`?

Yuriy Vidineev (adeptg) wrote :

Sure. Please find it in attachment

Kai-Heng Feng (kaihengfeng) wrote :

I guess something went south when NM is signaling "wireless-enabled" signal. The culprit can be either NetworkManager or NetworkManager-Applet.

How do you suspend your laptops?

Shih-Yuan Lee (fourdollars) wrote :

Dell XPS 13 9360 should be preloaded with kernel 4.4 + the generic xorg package instead of LTS Enablement Stacks [1].
But your system looks like LTS Enablement Stacks are installed according to the dpkg.log in comment #10.
Did you install LTS Enablement Stacks by yourself?


Yuriy Vidineev (adeptg) wrote :

Kai-Heng Feng, just closing the lid.

Shih-Yuan Lee, yes, I've installed by myself. I need recent kernel version for USB C docking stations support

Kai-Heng Feng (kaihengfeng) wrote :

Is this 100% reproducible?

Yuriy Vidineev (adeptg) wrote :

Kai-Heng Feng, yes

Yuriy Vidineev (adeptg) wrote :

One more detail: this bug is for wireless networks only. Looks like wired works as expected (please see "Dell docking" on screenshot)

Kai-Heng Feng (kaihengfeng) wrote :

I got XPS 9360 at hand, but unfortunately I can't reproduce the issue.

Can you try the latest Xenial (16.04) image here?

Yuriy Vidineev (adeptg) wrote :

Hi Kai-Heng!
I still see this bug. I'll try to reproduce it with liveUSB

Yuriy Vidineev (adeptg) wrote :

I wasn't able to reproduce it with liveUSB and only one Wi-Fi connection. Will try to add more connections (few openvpn probably)

Alfred (alf-redyoung) wrote :

From comment 40 in upper stream bug -
Upgrade to higher version(1.8) of NM should fix this. However xenial is stuck in 1.2.6... So I think 18.04 upgrade can fix this - which NM is 1.8.10.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.