nm-applet not refresh networks

Bug #150888 reported by tobiash
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager-applet (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I'm using ubuntu gusty amd64 and the nm-applet does not refresh the available networks anymore from time to time (as in feisty). So if I want to connect to an wireless network just created I have to reboot the computer. My suggestion is that this applet must have a refresh button.

06:02.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)

driver ndiswrapper

Thank you.
Tobias H.

Revision history for this message
Adrian (ruewan) wrote :

yup. It is really annoying to have to reboot to change networks. My apartment is accross the street from my job and I have to reboot my computer or create a manual connection when I want to connect switch from the wireless network at home to the one at work.

Revision history for this message
govinda6666 (ariccanfly) wrote :

same problem here, my workaround is to change from roaming mode to static.. but that only works for WEP/encrypted networks

Revision history for this message
Charlie Daly (cdaly) wrote :

I'd like to add my vote to this. Really annoying to have to reboot.

Revision history for this message
Sebastien Wains (sebastienw-deactivatedaccount) wrote :

Tonight I had to make some tests with a new access point and had to switch from my personal AP to the test AP a number of times.

I figured NM was no longer refreshing the wireless network list at all.
In earlier version of Ubuntu, it used to refresh the list after a small delay as far as I remember.

Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please add the /var/log/syslog to your bug report as an attachment? Also you can submit more information for it by looking to https://wiki.ubuntu.com/DebuggingNetworkManager , Thanks in advance.

Changed in network-manager-applet:
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.

Changed in network-manager-applet:
status: Incomplete → Invalid
Revision history for this message
rich (reakinator) wrote :

Reopening because I am having this problem in Ubuntu Gutsy, and will provide the requested information.

Changed in network-manager-applet:
status: Invalid → New
Revision history for this message
rich (reakinator) wrote :

I have noticed this problem since I switched from Feisty to Gutsy. I do not suspend my computer, but just close the lid (it goes blank) and go somewhere else (ie a cafe) and open back up, the old wireless connections are still showing. They still show (and nm-applet tries to connect to) the old no-longer available connections for, well I don't know exactly, but a long time. I normally just turn off/on the switch on the side of the laptop, but it still seems to take a while to refresh.

The syslog may show that I attempted a manual refresh with the command "iwlist eth1 scan". I don't know if this actually did anything, since nm-applet had already updated (after I was sitting in the cafe for about 10 minutes).

It would be nice if there was a manual refresh button, along with a setting to determine how often nm-applet is refreshed.

regards,
Rich

Revision history for this message
rich (reakinator) wrote :

This is quite a time-killer for me, as I move from coffee shop to home every day. Today it took about 30 minutes before nm-applet rescanned... just long enough for me to figure out how to do it manually from the command line (nm-applet seems to have some spite programmed in it).

I run:
iwlist eth1 scan

and I get all the wireless connections I want to connect to, while the previous ones are still showing in nm-applet, that no longer exist. What is more, I flip the manual wireless switch on the laptop, or turn off wireless on nm-applet, then return them back on and the non-existent connections are still showing!

nm-applet must a) be keeping its own records somewhere, other than what iwlist is getting its information from, and b) is not auto-updating for up to 1/2 hour at a time. Why?

-rich

Revision history for this message
Jess Bermudes (jbermudes) wrote :

I also experience this in Hardy. It gets especially annoying when i take the train because nm-applet adds every wifi AP it finds along the train ride and when I'm at my destination it's filled with old APs that are 20 miles away. A refresh list item would solve this perfectly.

Changed in network-manager-applet:
status: New → Confirmed
Revision history for this message
Alexander Sack (asac) wrote :

this isnt an issue in intrepid and beyond anymore. we have another issue which is similar, but is about suspend/resume. If you see that this is not your bug.

Changed in network-manager-applet:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.