Bug appears between 10：40～10：45: 05-24 10:40:04.794 24207 24207 D wpa_supplicant: nl80211: Received scan results (27 BSSes) 05-24 10:40:09.839 24207 24207 D wpa_supplicant: nl80211: Received scan results (21 BSSes) 05-24 10:40:14.864 24207 24207 D wpa_supplicant: nl80211: Received scan results (19 BSSes) Supplicant keeps notifying the scan results event, but nothing displayed in the UI.

James, are you aware of this bug? what's the analysis on your side?

Zhenqing has added log on my side now.

Is this bug the same as bug 979841?

(In reply to Zhenqing Liu from comment #1) > Bug appears between 10：40～10：45: > > 05-24 10:40:04.794 24207 24207 D wpa_supplicant: nl80211: Received scan > results (27 BSSes) > 05-24 10:40:09.839 24207 24207 D wpa_supplicant: nl80211: Received scan > results (21 BSSes) > 05-24 10:40:14.864 24207 24207 D wpa_supplicant: nl80211: Received scan > results (19 BSSes) > > Supplicant keeps notifying the scan results event, but nothing displayed in > the UI. Vincent, please comment here, why dose gaia show noting when receive scan result?

I don't reproduce the problem after several toggles. How is the reproduce rate of the bug ? BTW, can you attach the log again. I can't open the file.

I can't reproduce this too. Zhenqing, can you try again? And provide detail STR.

(In reply to Kai-Zhen Li from comment #8) > I can't reproduce this too. > > Zhenqing, can you try again? And provide detail STR. Sorry to say I can't reproduce too. Our tester has repoduced this twice. But according to the logs，I found they're both affected by the connecting tests with a web authentication network conducted before this. The connecting tests didn't seem to be terminated in a proper way, because the supplicant tried to associate with the web authentication network. So scan really began after association failed or disconnected. I've told the tester about the connecting affection and I'll keep track on this. If it doesn't come up for a few days, I think we can close it.

Never come up again. Close it.