nm-applet displays corrupted essids and multiple connected networks

[Loïc Minier]

Hi

At an event yesterday I saw nm-applet misbehave, even after sudo stop network-manager + sudo start network-manager, killing + relaunching nm-applet and modprobe -r iwlagn + modprobe iwlagn.

I will attach a screenshot of the corruption which occurred regularly. iwlist scan showed no such corruption.

Bye

ProblemType: Bug
Architecture: amd64
CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
Date: Sat Oct 3 16:48:12 2009
DistroRelease: Ubuntu 9.10
IpRoute:
 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.118 metric 2
 169.254.0.0/16 dev wlan0 scope link metric 1000
 default via 192.168.0.254 dev wlan0 proto static
Package: network-manager-gnome 0.8~a~git.20090923t220421.1ac8ffd-0ubuntu4
ProcEnviron:
 LANGUAGE=fr_FR:fr:en_GB:en
 PATH=(custom, user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/zsh
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
SourcePackage: network-manager-applet
Uname: Linux 2.6.31-11-generic x86_64
WpaSupplicantLog:

[Alexander Sack (asac)]

i saw this too at some point when developing the applet improvements. thought it was fixed. if you have this again, please run valgrind (NM and applet) to check for bad mem access.

[Alexander Sack (asac)]

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 :)

[Alexander Sack (asac)]

if we already have that commit just move back to applet. thanks!

[Štefan Baebler (stefanba)]

it also shows random ESSIDs with ad-hoc networks.