touch-packages team mailing list archive

[Tony Espy <1478009@xxxxxxxxxxxxxxxxxx>]

I extended this bug description to cover the fact that NM is prevented
from auto-connecting to another known, available AP.

** Tags added: hotspot

** Summary changed:

- creating a hotspot should disconnect from the current AP
+ creating a hotspot should disconnect from the current AP & prevent NM from auto-connecting to another known AP

** Description changed:

  When creating a new hotspot using the attached script, NM no longer
  disconnects from the current AP.  I'm sure I've looked at this sometime
  in the past and confirmed it wasn't connected, so this behavior has
  changed at some point.
  
  I tested this on arale rc-proposed image 68
+ 
+ krillin (stable, #24 ) will cause the current AP to disconnect, however
+ if another known AP is available, it will re-connect.

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

Title:
  creating a hotspot should disconnect from the current AP & prevent NM
  from auto-connecting to another known AP

Status in Canonical System Image:
  New
Status in indicator-network package in Ubuntu:
  New

Bug description:
  When creating a new hotspot using the attached script, NM no longer
  disconnects from the current AP.  I'm sure I've looked at this
  sometime in the past and confirmed it wasn't connected, so this
  behavior has changed at some point.

  I tested this on arale rc-proposed image 68

  krillin (stable, #24 ) will cause the current AP to disconnect,
  however if another known AP is available, it will re-connect.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478009/+subscriptions