@Alan: network-manager-gnome was already at the latest version, the one
mentioned by Robert above. But I also upgraded to everything xenial-
proposed had 30 mins ago (thinking maybe you did that) and still no
luck.

But this is how I made this version work for me (@Robert, maybe you'd like to 
test this?):
a. reboot (just to make sure we all start from the same point - I noticed it 
matters here)
b. open a terminal  and $ sudo systemctl restart NetworkManager.service
c. test wifi off/on and suspend/resume - now NM works perfect for me (didn't 
test AP off/on as I can't do that now).
This workaround also works if between a. and b. you perfom c. to check if it 
works (which isn't for me).

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

Title:
  [SRU]network-manager

Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  NM needs to re-read the DEVTYPE after the device name changed, an example is 
that WiFi network list disappears from network manager applet

  Steps to reproduce: -

  1. Connect to a WiFi AP.
  2. Switch off the AP OR switch off the wifi in the computer.
  3. Switch point (2) back on.
  4. The network will get connected to the AP it was connected to in point (1).

  Problems:-

  1. The network manager applet does not show the list of WiFI APs it can find.
  2. The network manager applet does not the name of the AP to which it is 
connected
  3. The icon of the applet shows two vertical arrows in opposite direction - 
the wired connection symbol and NOT the wifi connected icon.

  Temporary Workaround:-
  Log out and again log back in.

  [Testcase]

  After upgrading to the new version, the repeating the above steps
  should give expected behavior.

  [Regression Potential]
  Potential of causing regression is relatively small for a one line change to 
re-read a value to be known.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1574347/+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

Reply via email to