** Changed in: wpa (Ubuntu Wily)
       Status: Fix Committed => Triaged

** Changed in: wpa (Ubuntu Wily)
       Status: Triaged => Won't Fix

You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs

  No wifi connection after suspend with systemd due to missing "wpa_cli

Status in One Hundred Papercuts:
  Fix Released
Status in NetworkManager:
Status in wpa package in Ubuntu:
  Fix Released
Status in wpa source package in Wily:
  Won't Fix
Status in wpa source package in Xenial:
  Fix Released

Bug description:
  Using systemd as my default init system if I resume from suspend my
  laptop, it doesn't automatically reconnect to the wireless network and
  it doesn't list the available network connections.

  The only way to get a wireless connection is to restart the network-
  manager daemon or going to the gnome-control-center, disable wireless
  and enable it again.

  In some of these cases this bug can be worked around by calling "wpa_cli 
suspend/resume" before/after suspend, like we used to do with the old pm-utils 
quirks (/usr/lib/pm-utils/sleep.d/60_wpa_supplicant). This only affects 
particular hardware, and thus this needs to be tested by affected reporters, 
there is no general reproducer for arbitrary systems.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager
  Uname: Linux 3.19.0-031900-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  Date: Sun Feb 15 18:27:39 2015
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-10-22 (116 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
   default via dev wlan0  proto static  metric 1024 dev wlan0  proto kernel  scope link  src dev wlan0  scope link  metric 1000
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-01-13 (32 days ago)
   DEVICE   TYPE      STATE        DBUS-PATH                                  
CONNECTION       CON-UUID                              CON-PATH
   wlan0    wifi      connected    /org/freedesktop/NetworkManager/Devices/2  
openhost_caldas  09d1f69d-d3da-4978-a69c-d94455db7ecf  
   docker0  bridge    unavailable  /org/freedesktop/NetworkManager/Devices/3  
--               --                                    --
   eth0     ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  
--               --                                    --
   lo       loopback  unmanaged    /org/freedesktop/NetworkManager/Devices/0  
--               --                                    --
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:

Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to     : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

Reply via email to