Comment 104 for bug 548992

I want to add support to the fix that involves removing network manager (network-manager-gnome),
Removing network manager worked for me.

Last night I upgraded from a working Ubuntu karmic koala installation to Ubuntu 10.04 LTS (lucid).

In the morning the wireless usb would not associate anymore.
I got the "dread message" in dmesg
wlan1: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (reason 3)
[It is important to point out that this message made me suspicious because earlier in dmesg
it had shown the wireless associating and authenticating to the access point ... so I knew
that drivers were probably OK]

Here is how the adaptor identifies to lsusb
(Belkin Components Wireless G Plus MIMO Network Adapter)

Here is an excerpt from dmesg showing the drivers used.
[ 15.114787] Registered led device: rt73usb-phy0::radio
[ 15.114800] Registered led device: rt73usb-phy0::assoc
[ 15.114812] Registered led device: rt73usb-phy0::quality

But of course ... none of this was the problem.

The MOMENT that network-manager-gnome was deinstalled I was associated with the network
and could ping local computers. In my case, before I could get Google to work, I had to fix
resolv.conf.

I think if you are using DHCP you would not need this (and most of you are ... if you don't know what
it is, you definitely are!). However, I have a manually configured network and assigned ip addresses, and
of course network manager had been handling my resolv.conf. So after removing network manager
I had to add to resolv.conf the line

nameserver 10.0.134.1 (that's my nameserver ... not yours!)

Then it all worked.

 I kind of hate network manager ... it causes as many problems as it fixes.