NetworkManager attempts to connect to unavailable previously connected network when resuming from suspend
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: network-manager
On Kubuntu Karmic, if I suspend my computer while connected to a wireless network and then resume it in a different location without that wireless network, the computer will attempt (but fail, obviously) to connect to the same network it used to be connected to. Even after it fails, this network will remain in the list until KDE or the computer is restarted. If another wireless network is available, NetworkManager will still try to connect to the unavailable one, only connecting to the available one after the first attempt fails. My wireless card is a Intel 4965 using the latest driver from compat-wireless, but the problem occurs with all drivers. I have also tried using later upstream versions of the Network Manager plasmoid, but these do not affect the problem.
description: | updated |
This happened to me on intrepid/ jaunty/ karmic when I switched to the ath5k driver. I have this problem right now. I don't think it's networkmanager's fault. It seems the previous connected network shows up in the scanning list before real networks do, and then it doesn't go away. I'm on a thinkpad sl300 with atheros ar5007EG, 242x, running 2.6.30-8.
02:00.0 Ethernet controller: Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter (rev 01)