network-manager-applet doesn't update AP list or autoconnect
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager-applet (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
This is in the latest Intrepid for both 64 and 32 bit intel.
At least it does not do so consistently. I come into work, turn on my AP, then either have to wait several minutes, or do "sudo iwlist scan" in a terminal, or tell it to connect to a "hidden" network which is NOT hidden.
There is no "refresh AP list".
In the environment we are testing wireless devices so there are a dozen ESSIDs or more visible.
Sometimes it picks up every AP (like when I drive leaving my laptop on, I see the businesses - hotels, restaurants, etc. - with open APs). Then it doesn't see the one at my desk. Those stale APs are in the list, but not the one at my desk, so the refresh feature is needed for this case too.
Manually doing "sudo iwlist scan" has always fixed it. Whatever mechanism for doing the equivalent should be available in the applet (without having to authenticate, at least not more than once).
Also, (comparing to my Nokia n810 tablet), it doesn't automatically reconnect to APs - it should have a way of marking my desktop and home AP as "autoconnect" so by the time I open my computer it would have switched the connection. This might be higher up that the applet, but that is where it would be visible.
I have the same problem with Ubuntu 9.04 alpha 3
I have only one wifi network (open, with no encryption and visible essid), but often the gnome applet doesn't attach to it, and list no wifi network available.
I tried to create a new wifi network with the applet, but it doesn't attach, but if I open the combo about "Connection" I find the netword essid (I don't know if this happens because of I tried to create it before), select it and press "Create" the system get connected.
Usually "sudo iwlist scan" fix the problem, and the networkmanager attach to network automatically.