Network manager showing no list of wifi networks after resume from suspend
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Ubuntu 16.10 on Dell XPS 13 9350 (Skylake) with Intel 8260 wifi card. When resuming after supsend, network manager does reconnect to the last wifi but does not show this in the tray icon. Also the menu underneath the icon does not list any wifi networks anymore.
A
sudo service network-manager restart
solves the issue most of the times, but not always.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: network-manager 1.2.4-0ubuntu1
ProcVersionSign
Uname: Linux 4.8.0-27-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Nov 27 20:20:54 2016
EcryptfsInUse: Yes
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2016-07-30 (120 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
IpRoute:
default via 192.168.123.205 dev wlp58s0 proto static metric 600
169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
192.168.123.0/24 dev wlp58s0 proto kernel scope link src 192.168.123.15 metric 600
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to yakkety on 2016-10-30 (27 days ago)
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH
virbr0 bridge connected /org/freedeskto
wlp58s0 wifi connected /org/freedeskto
lo loopback unmanaged /org/freedeskto
virbr0-nic tun unmanaged /org/freedeskto
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
running 1.2.4 connected started full enabled enabled enabled enabled enabled
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1636282, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report.