This one has annoyed me for quite a while now (well before 15.x). Having to disable/enable wifi to get network manager applet to see the wifi ssid (or wait quit a while) is a bit of a pain and shouldn't be necessary for a modern OS. Also, the fact that there is no way anywhere, either in network-manager applet or in network manager itself (network settings), to force a refresh really sucks.
My network manager applet disappeared for a while (until I worked out how to fix that) so to get my lappy to see my wifi I had open Network Settings, click "Connect to a hidden network", then select the ssid from the drop down list of known networks. Not exactly convenient! So a "scan now" button would be great, along with more frequent automatic wifi scanning. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1491612 Title: doesn't scan for available wifi networks often enough + no way to manually force a scan Status in One Hundred Papercuts: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Steps to reproduce: - turn on a wifi router nearby - click on the network applet icon Expected behavior: As soon as the new network becomes available, it should become visible in the list within few seconds (and if it is a network you have already configured and set to automatically connect to, it should connect) Observed behavior: You won't see the network show up in the list, or perhaps it will, after a few minutes. Way too much time. Additionally, there should be an item in the menu such as "scan for networks now" to force scanning for available networks. But there's no such thing even. So the only workaround is to physically disable and reenable wifi on hardware, if your computer has a button for that. That will trigger re-scanning for available networks. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.1 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Sep 2 23:48:42 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-11 (691 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) IpRoute: default via 192.168.1.1 dev wlan0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.167 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-08-15 (18 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-02-20T16:52:59.722501 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/2 Sixty-Seven 2dfa6e3a-076f-48f9-a40c-d182c47e4178 /org/freedesktop/NetworkManager/ActiveConnection/0 43:29:1A:07:53:91 bt disconnected /org/freedesktop/NetworkManager/Devices/3 -- -- -- eth0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- -- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1491612/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp