Network Indicator sometime shows APs that aren't available in scan results

[Pat McGowan]

Resuming the device in a new location with new access points does not result in the currently available access points displayed in the network pulldown

The nm demon may need to react to the events from powerd, although I am surprised there is no periodic rescan when no connection is active

[Josh Leverette (coder543)]

What about rescanning when pulling down the network list in addition to powerd events? By the time the user pulls down the network list, they may have just gotten off of a moving vehicle after reading an ebook for the past half hour and decided that there is a nearby network, regardless of the fact that they haven't caused any powerd events to fire recently.

Rescanning by powerd would ensure a high probability of the network list already being accurate, but refreshing on pull down would give the user the desired results a few moments later if the powerd-triggered scan hadn't already done so.

[Tony Espy (awe)]

@Pat

Can you please add a build # and device to your description?

Also, how did you put the device to sleep? Did you verify that it actually went into suspend? AFAIK, we have a bug where the mako never actually suspends due to a driver wake_lock. I haven't tested the latest images with maguro, but will give it a try to tomorrow.

That said, I'm pretty sure this is an indicator bug, not a Network Manager bug. I created an upstart job with a simple script which sleeps for 10 seconds, and then runs the command 'nmcli dev wifi' to grab the latest scan list. I rebooted the phone, then took a walk around the block. When I came back inside, I had a good ~10-15m worth of scan output logged to /var/log/upstart/wifi-scan.out. Looking at the output, the scan list is indeed being updated as expected. My guess is that backend indicator network code ( ie. chewie-network ) isn't doing the right thing, and never cleans up APs that are no longer available in the scan results.

You do bring up a good point about Powerd and NM reacting to events from it. This is something that still needs to be looked at.

[Pat McGowan (pat-mcgowan)]

This was reported in build 153 on a mako
testing on saucy-19 today and cannot reproduce it.

[Tony Espy (awe)]

Re-opened and assigning to Ted for now.

I *think* this may be an issue where it always shows previously connected APs in the list, even if they are no longer present in the scan list.

[Ted Gould (ted)]

I don't think we're showing anything other than scan results. Though it would take us a bit to update after suspend, it seems unlike that was it. Considering the age of this bug, I think it might actually be a QMenuModel issue. Though we've since switched to Unity Menu Model. Can anyone recreate this on a modern image?

[Launchpad Janitor (janitor)]

[Expired for Network Menu because there has been no activity for 60 days.]