touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #92221
[Bug 1478009] Re: creating a hotspot should disconnect from the current AP
I re-tested a fresh flash of krillin ( stable, #24 ). I made sure to
remove any connections found in /etc/NetworkManager/system-connections
before testing as well.
I no longer see the re-connection problem. I've verfied that that if
connected to a WiFi AP when hotspot is enabled, it properly disconnects.
So I think this bug is arale-specific.
That said, I did find that the indicator doesn't prevent you from
connecting to a WiFi AP that appears in the scan list ( note, the list
eventually becomes empty, so you have to do this right away ). Also, if
another AP is available that you've previously connected to, although
the first AP is disconnected, nothing prevents NM from connecting to the
second AP. I'll enter separate bugs for both of these.
--
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
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478009/+subscriptions
References