@Matthew Regarding comment #18. Yes, NM does regular scans automatically. Over time, if it's not able to connect to an AP, the scan interval is gradually increased up to a maximum of 2m between scans. A long time ago, there used to be a method that nm-applet would use to tell NM that the user was interacting with the UI, which would in turn cause the scan_interval to revert back to it's minimum ( note, this may have just happened when the GetAccessPoints method was invoked ), but at some point a RequestScan method was added. I'm not sure if there's a trigger to cause the scan_interval to revert to minimum anymore.
We could add logic to the indicator to request a scan, however there's no way I can see to easily coordinate this with the current NM auto-scan logic. NMDeviceWiFi doesn't appear to export it's internal 'Scanning' property, nor does it export the current scan interval. It may be that the we can change the cull_scan_list function to remove the AP when wpa_supplicant indicates that a BSS has been removed, although this might cause issues with roaming configurations as there might be other BSSes in the same SSID group ), or we could lower the prune_scan_interval... Fixing this logic is probably the most promising short-term fix. Long term, getting the removal to approach that of OS X or Android ( <= 30s ) will definitely involve the indicator in some way... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1425172 Title: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min) Status in Canonical System Image: Confirmed Status in indicator-network package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Status in network-manager package in Ubuntu RTM: Invalid Bug description: Summary: Network indicator lists the non-exist AP Steps to reproduce: 1. Boot to system 2. Scroll down the Network indicator 3. It lists about 10 AP (In Taipei office) 4. Go to another place and check network indicator again Expected Result: It should not list non-exist AP and only show available AP Actual Result: It shows about 12 AP on the screen but only two are real AP for connecting, and others 10 are from last list. This is reproducible on mako/krillin on both RTM and vivid. The main issue is that the timeout for the AP to be removed from the known AP list is too big when comparing with other phones. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1425172/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
