network manager wont scan network list after suspend
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: network-
Hy!
I'm on an up-to-date Jaunty amd64 system with a Dell 1310 that has a Broadcom-based wireless card. It uses the Broadcom sta driver (wl).
My problem is that NetworkManager won't (re)scan the wireless network list after I resume my computer from suspend; instead it tries to connect to the last used network... which is fine if I stay in the same place, but if I take my computer to another location while it's suspended, it immediatelly tries to connect to the nonexistent (at the new place) last used network... then it scans the network list, and as soon as the first connection attempt is finished (soo looong) it connects to my prefered network automatically... but if I don't want to wait, I have to choose the network by hand...
So I think nm-applet should wait for the network to appear on the network list before tries to connect it after suspend... it meens a little wait if the location won't changed, but solves a much longer, on a new location...
(I'm talking about non hidden networks of course!)
Thanks for your help!!
$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
$ apt-cache policy network-
network-
Installed: 0.7.1~rc4.
Candidate: 0.7.1~rc4.
Version table:
*** 0.7.1~rc4.
500 http://
100 /var/lib/
affects: | network-manager-applet (Ubuntu) → network-manager (Ubuntu) |
description: | updated |
This annoys me too. I agree, it should rescan the networks as it would on a boot and connect automatically after that.