desktop-packages team mailing list archive

[Magnus Hoff <1270257@xxxxxxxxxxxxxxxxxx>]

The workaround I am currently using is to use the b43-driver instead of
wl (sudo rmmod wl ; sudo modprobe b43). This means forgoing support for
802.11n, I think. At least I can no longer see 5GHz networks. However,
it also means that the network reliably reconnects after suspend and
resume, in my experience.

(Hardware: 13" Retina MacBook Pro, software: Kubuntu 15.04)

-- 
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/1270257

Title:
  NetworkManager failed to function after suspend and resume

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  NetworkManager failed to function after resuming from suspend. The
  indicator applet in the Mac OS style menu bar showed the empty
  quarter-circle, and clicking "Enable Networking" didn't change the
  menu options or the style of the applet. Running "sudo service
  network-manager restart" brought back functionality.

  $ dpkg -l systemd* logind*
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name                   Version          Architecture     Description
  +++-======================-================-================-==================================================
  un  logind                 <none>                            (no description available)
  un  systemd                <none>                            (no description available)
  ii  systemd-services       204-0ubuntu19.1  amd64            systemd runtime services
  ii  systemd-shim           6-0ubuntu0.13.10 amd64            shim for systemd

  
  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: network-manager 0.9.8.0-0ubuntu22
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Fri Jan 17 10:08:48 2014
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2012-10-18 (456 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.14  metric 9 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to saucy on 2013-11-06 (72 days ago)
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-11-05T17:49:23
  nmcli-dev:
   DEVICE     TYPE              STATE         DBUS-PATH                                  
   wlan0      802-11-wireless   connected     /org/freedesktop/NetworkManager/Devices/1  
   eth0       802-3-ethernet    unavailable   /org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING         VERSION    STATE           NET-ENABLED   WIFI-HARDWARE   WIFI       WWAN-HARDWARE   WWAN      
   running         0.9.8.0    connected       enabled       enabled         enabled    enabled         disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1270257/+subscriptions