Public bug reported:

After upgrading from Ubuntu 14.04 to Ubuntu 16.04, the Network manager
behaviour changed regarding to the priorities of networks.

I have several AdHoc-network definitions, that are now activated in
favor of my home WiFi connection. I had to remove the autoconnect option
on all of them, as even after using Ubuntu 16.04 some time,
NetworkManager still sometimes decided to pick one of the AdHoc
connections in favor of the home WiFi (the AdHoc networks are
established anew, there is no such network available for scanning).

Maybe if NetworkManager now uses a new system, the update process should
change the settings of each connection accordingly.

I however wonder if this is a deeper bug, making the old behaviour
impossible (to autoconnect to an existing AdHoc network if available,
but connect to the default AP if not).

** Affects: network-manager (Ubuntu)
     Importance: Undecided
         Status: New

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

Title:
  networkmanager priority changes on dist upgrade to 16.04

Status in network-manager package in Ubuntu:
  New

Bug description:
  After upgrading from Ubuntu 14.04 to Ubuntu 16.04, the Network manager
  behaviour changed regarding to the priorities of networks.

  I have several AdHoc-network definitions, that are now activated in
  favor of my home WiFi connection. I had to remove the autoconnect
  option on all of them, as even after using Ubuntu 16.04 some time,
  NetworkManager still sometimes decided to pick one of the AdHoc
  connections in favor of the home WiFi (the AdHoc networks are
  established anew, there is no such network available for scanning).

  Maybe if NetworkManager now uses a new system, the update process
  should change the settings of each connection accordingly.

  I however wonder if this is a deeper bug, making the old behaviour
  impossible (to autoconnect to an existing AdHoc network if available,
  but connect to the default AP if not).

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to