Comment 4 for bug 776952

commit 2249b011432ca3dcce112f0f71e0f531b4bb9347 in the 3.1 series fixes it for me. See https://lkml.org/lkml/2011/9/28/666 for discussion.

Thus I suggest pulling said commit.

What is interesting for me, and the reason why I reported it as a wpa_supplicant/NM bug is, that the original commit that this patch reverts was actually present in the kernel that I ran (2.6.39 - unsupported, I know) under Maverick, but the untoward behaviour only manifested itself on upgrading to Natty, which has a kernel (2.6.38) with this change, but that was still outdated relative to 2.6.39 that I was running, so I booted *with that exact same kernel* that I had used to download all the packages to upgrade to Natty under Maverick with no problems, but upon booting Natty (with that 2.6.39 kernel), the problem manifested itself immediately.

Thus, to work with upstream to find out why this seemingly benign change *that didn't cause trouble under Maverick* actually *is* a problem, looking into differences between wpa_supplicant/NM from Maverick to Natty could be beneficial.