touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #97349
[Bug 1478009] Re: creating a hotspot should disconnect from the current AP & prevent NM from auto-connecting to another known AP
This bug was fixed in the package indicator-network -
0.5.3+15.10.20150818-0ubuntu1
---------------
indicator-network (0.5.3+15.10.20150818-0ubuntu1) wily; urgency=medium
[ Pete Woods ]
* Link flight, WiFi and hotspot toggles. (LP: #11478159)
* Add properties for when different toggles should be enabled. (LP: #1478159)
* Add hotspot button
* Add icon to show when hotspot is enabled (LP: #1485491)
* Clean up connection from connectivity service to manager
* Disconnect from access points when starting hotspot (LP: #1478009)
* Enable Wifi when activating hotspot
-- CI Train Bot <ci-train-bot@xxxxxxxxxxxxx> Tue, 18 Aug 2015 08:46:29
+0000
** Changed in: indicator-network (Ubuntu)
Status: In Progress => Fix Released
--
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:
In Progress
Status in indicator-network package in Ubuntu:
Fix Released
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
References