I can confirm that this also happens when toggling the radio killswitch
on my x230 with Xenial:

Jul 26 09:48:19 Host NetworkManager[2979]: <info>  [1469540899.8669] manager: 
WiFi now enabled by radio killswitch
Jul 26 09:48:19 Host kernel: [71025.599893] IPv6: ADDRCONF(NETDEV_UP): wlan0: 
link is not ready
Jul 26 09:48:19 Host wpa_supplicant[3344]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
Jul 26 09:48:19 Host wpa_supplicant[3344]: dbus: Failed to construct signal
Jul 26 09:48:19 Host NetworkManager[2979]: <info>  [1469540899.9049] device 
(wlan0): supplicant interface state: starting -> ready
Jul 26 09:48:19 Host NetworkManager[2979]: <info>  [1469540899.9050] device 
(wlan0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
Jul 26 09:48:19 Host kernel: [71025.639368] IPv6: ADDRCONF(NETDEV_UP): wlan0: 
link is not ready

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1585863

Title:
  WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
  required to fix it.

Status in NetworkManager:
  New
Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Description:    Ubuntu Yakkety Yak (development branch)
  Release:        16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2
  libnm-glib4:amd64       1.2.2-0ubuntu2
  libnm-util2:amd64       1.2.2-0ubuntu2
  libnm0:amd64    1.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

  Reproduce steps:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 
--s3-delay-delta=5

  Expected result:
  The WiFi still functioned.

  Actual result:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  P.S. Ubuntu 16.04 also has the same issue.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to