some input from wiseman dan:
03:01 < dcbw1> asac: that issue is usually underneath in the driver. the only
times I've seen it are when you don't have the
wpa_supplicant update to ensure that the random SSID/MAC isn't
sent when exiting adhoc mode
03:02 < dcbw1> asac: the random ssid/mac is sent to ensure the driver
disconnects completely because wext sucks
03:02 * dcbw1 finds the commit
03:02 < dcbw1> I'm sure you have it already
03:03 < dcbw1> basically, if some *other* machine in range doesn't have that
commit, you'll se this
03:03 < dcbw1> it may not actually be the machine from the bug report
03:03 < asac> dcbw1: yeah. i agree that its probably under the scene
03:04 < asac> dcbw1: so tis triggered by adhoc nets?
03:04 < dcbw1> supplicant commit 64a04447c3d2248ab1aac7f6c220346dad0e1921
03:04 < dcbw1> wext: don't force-disconnect in ad-hoc mode
moving to supplicant :)
** Changed in: network-manager-applet (Ubuntu)
Status: New => Triaged
** Package changed: network-manager-applet (Ubuntu) => wpasupplicant
(Ubuntu)
--
nm-applet displays corrupted essids and multiple connected networks
https://bugs.launchpad.net/bugs/441427
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
