Here is how nm-applet looks after restart (killall nm-applet && nm- applet &)
** Attachment added: "Here is how nm-applet looks after restart" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748812/+attachment/5053391/+files/Screenshot%20from%202018-02-11%2019-50-55.png -- 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/1748812 Title: cannot view wifi networks after resume from suspend Status in network-manager package in Ubuntu: New Bug description: Hello, 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 DEVICE TYPE STATE CONNECTION 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 https://bugs.launchpad.net/ubuntu/+source /network-manager/+bug/1589401 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 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes IfupdownConfig: # 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 IpRoute: default via 192.168.1.1 dev wlp58s0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlp58s0 proto kernel scope link src 192.168.1.137 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH 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 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
