5GHz network is not available after suspend by closing lid
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Dell Sputnik |
New
|
Undecided
|
Unassigned | ||
network-manager (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Model: Dell XPS 13 - 9343
Network controller: Broadcom Corporation BCM4352 802.11ac Wireless Network Adapter (rev 03)
Action: close lid of laptop to suspend, open lid to resume
Expected behavior: Wireless would resume with access to 2.4Ghz and 5Ghz networks
Actual Behavior: Wireless resumes, but 5Ghz networks are not detected
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: network-manager 0.9.10.
ProcVersionSign
Uname: Linux 3.19.0-31-generic x86_64
NonfreeKernelMo
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Oct 26 21:08:17 2015
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2015-10-25 (1 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
IpRoute:
default via 192.168.1.1 dev eth0 proto static metric 100
169.254.0.0/16 dev eth0 scope link metric 1000
192.168.1.0/24 dev eth0 proto kernel scope link metric 100
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH
Wired connection 1 6c91668c-
Nexus 4 Network 4c6152f2-
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH
eth0 ethernet connected /org/freedeskto
98:D6:F7:2E:39:53 bt disconnected /org/freedeskto
wlan0 wifi disconnected /org/freedeskto
lo loopback unmanaged /org/freedeskto
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'.
1) If anything bug #1585863 is a duplicate of this bug -- this one was reported first. This bug reported 2015-10-26 and #1585863 2016-05-25
2) This is different hardware than #1585863 so even though the result is the same I am not certain that this should be a duplicate.