Created attachment 567527 [details] screenshot of "too many wifi networks" Description of problem: I live in an apartment building with many (40+) Wifi network SSIDs broadcasted. The nm-applet, as part of NetworkManager-gnome, displays too many SSIDs before it falls back to the 'More...' link to expand the list of networks, in order for my screen to allow for space to also list the Mobile Broadband and VPN connections configured. Version-Release number of selected component (if applicable): $ rpm -qf $(which nm-applet) NetworkManager-gnome-0.9.2-1.fc16.x86_64 How reproducible: Every time, consistently Steps to Reproduce: 1. Go into an area with many Wifi networks 2. Click nm-applet icon 3. Attempt to get to the Mobile Broadband / VPN section of the nm-applet network selection dialog. Actual results: Please see attached screenshot. Expected results: Truncate the list of wifi networks (~5-10 maybe?) and display "More...". Perhaps this also depends on the screen size (I'm on 1366x768).
This is a screenshot of new gnome network indicator, which is part of gnome-shell. It's the replacement of nm-applet for Gnome3. So, rather please report $ rpm -q gnome-shell
gnome-shell-3.2.2.1-1.fc16.x86_64
*** Bug 802728 has been marked as a duplicate of this bug. ***
This behavior is affecting me as well. I've bumped the severity to high as it's a fairly serious problem for me as I work remotely and without access to the VPN I cannot log into my work systems. One unusual thing about the behavior is that the network list often displays only a small number (~5) of SSIDs, although I'm fairly certain that the number of visible SSIDs doesn't vary that widely. If there's a workaround, I'd love to hear about it. I'm also running gnome-shell gnome-shell-3.2.2.1-1.fc16.x86_64.
FWIW, I just powered my laptop off, waited a few seconds and powered it on again, and now I have only 11 SSIDs showing + More..., and then VPN Connections, etc. I'm assuming that's a viable workaround, so I'm dropping the severity back to medium.
*** Bug 801185 has been marked as a duplicate of this bug. ***
FWIW, this problem seems to no longer occur in GNOME 3.4 (Fedora 17)
Yes, it appears to be fixed in 3.4.