New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 888070 link

Starred by 4 users

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Uber tray does not load all the Wifi networks in range.

Project Member Reported by jmuppala@chromium.org, Sep 21

Issue description

Chrome Version: <From about:version: Google Chrome 70.0.3538.28>
Chrome OS Version: <From about:version: Platform 11021.23.0>
Chrome OS Platform: <Coral/Santa>

Please specify Cr-* of the system to which this bug/feature applies (add
the label below).

Steps To Reproduce:
(1)Enable Wifi and check the available networks.
(2)displays only 11-12 networks in an area that has ~30 wifi networks
(3)after the wifi refresh, adds couple more networks but does not show all 30 networks.
(4)happens in uber tray and chrome://settings/network

Expected Result:
Should display all available networks
Actual Result:
displays only 11-12 networks 


Note: 
After every wifi refresh, goes back to displaying 11-12 networks, and then adds few at a time.


 
How many networks are listed in chrome://settings/networks?type=WiFi ?

it matches with the networks listed on uber tray.


Components: -UI>Shell>Networking -UI>Shell>StatusArea
In that case, Shill is (probably intentionally) limiting the number of networks provided to Chrome. I suspect this is WAI but will defer to the Shill folks.


Labels: M-71
seeing this issue on Nocturne 11105.0.0, 71.0.3562.0
This bug does not have an owner and is marked RBS. Please update with the plan and ETA to fix the issue or remove the RBS label if this is no longer a blocker. Thanks.
Cc: benchan@chromium.org
Owner: kirtika@google.com
Status: Assigned (was: Unconfirmed)
Kirtika, assigning this to you to take a look. Please reassign if needed. Thanks
Seeing this issue on Eve (11117.0.0, 71.0.3565.0)
Friendly ping, are we going to be able to fix this on M70? Thanks.
I am still seeing this on R70-11021.45.0, 70.0.3538.58. 
The uber tray and chrome://settings/network lists only ~10 networks first and then loads up couple more 
1)if wifi toggle is turned off and on 
2)in couple of minutes loads few at a time.

again, after reboot/powerwash/loading new image this starts over from ~10 networks.
@kirtika, will we be able to get this into M70? Thanks
Owner: steve...@chromium.org
Jeevitha: Does an "iw wlan0 scan | grep SSID" on the command line give you the full list of networks? 

I recall another thread where Steven found that shill wasn't returning the full list over dbus. Assigning to Steven to check if its a UI thing or if possible, give me a way to find where shill is failing.

Owner: kirtika@chromium.org
The UI should only be limiting the number of networks in the UI to 100. I am fairly certain this is not a UI bug. A Feedback report would help investigate.

Hi Kirtika,  "iw wlan0 san | grep SSID" also lists only ~10 networks (matches with the uber tray)

localhost / # iw wlan0 scan | grep SSID
        SSID: CrOS_Buffalo_5GHz
        SSID: GIN-2g-poor
        SSID: GIN-3g
        SSID: Google-A
        SSID: JamGuest
        SSID: CrOS_Cisco_AP3504
        SSID: GIN-3g
        SSID: Google-A
        SSID: GoogleGuest
        SSID: GIN-2g-poor
        SSID: GIN-2g
        SSID: GoogleGuest


but actually there are close to ~30 networks.
After couple of scanning, wifi toggle off/on, the number of networks increases in both uber tray and "iw wlan0 san | grep SSID".

Nocturne - 11151.4.0, 71.0.3578.8

this happens with both cases ie.,shill sandboxing flag enabled and disabled.
seeing this on Kevin -11021.51.0, 70.0.3538.69
Labels: -M-70
Per chat with kirtika@ offline, moving this to M71.
Seeing this issue on M71-11151.16.0, 71.0.3578.27-Nocturne.

The network list had only 13 networks for approx 3-4 minutes .ie.,for multiple  wifi scans, then after wifi toggle off/on listed around 30 networks.

Again after few wifi scans, went back to only 10-12 networks. 

Because of missing networks, unable to connect to our required test networks, having to turn off/on wifi toggle multiple times. 

@Kirtika Please find the debug logs attached.

debug-logs_20181030-160155-nocturne.tgz
4.2 MB Download
<Bulk edit> Reminder M71 Stable is approaching. Please review this bug and assess if this is indeed a RBS. If not, please remove the RBS label. If so, please make sure any planned work will be tested in Beta and verified before the Stable date. Thanks
Feedback sent #issue 888070

It should be a long list living in a condo. Most notably, the free condo Xfinity wifi network is not on the list.

Google Chrome	71.0.3578.49 (Official Build) beta (64-bit)
Revision	874bcb033a70ecd8537551058f70a528c20bb17d-refs/branch-heads/3578@{#629}
Platform	11151.29.0 (Official Build) beta-channel caroline
Firmware Version	Google_Caroline.7820.384.0
Screenshot 2018-11-15 at 1.43.44 PM.png
61.2 KB View Download
Labels: Hotlist-ConOps-CrOS
Here is a feedback report: https://listnr.corp.google.com/report/85788810427
After toggling wifi off/on, I get 2 more networks. Should be more.

The first two networks are mine, CB and Armond.
Screenshot 2018-11-15 at 2.13.18 PM.png
68.3 KB View Download
@kirtika - Can you please provide an update for this issue? This is marked RBS and stable is approaching soon. Thanks

Cc: briannorris@chromium.org
Jeevitha, can you confirm if this is a regression?
I saw the repro at Jeevitha's desk, `watch -n2 "iw wlan0 scan dump | grep SSID | wc -l` gives an idea of the problem. That command returns the # of SSIDs seen, and it varies from 30+ to under 5. 
This is semi-expected if we are issuing scans more frequently than {1/time it takes for wifi NIC to complete a full scan}. 
one way to proceed here would be to check if we've added more scan requests b/w R69 and R70 (assuming R70 was the regression). 
Brian, Steven: thoughts? 

Ping since this is very late into M71 and we need to get this moving...  
Also, per #27, this isn't a M71 regression and shouldn't be tagged as a M71 RBS.
This was originally reported on M70 as a new regression but was not fixed and is reproducible in all M70+ milestones.
Labels: -ReleaseBlock-Stable
IMportant to fix this but if it's not a regression it shouldn't be RBS.
Labels: M-72 M-70
Yes this was a M70 regression, M70 and up milestones are still seeing this issue. 

Sign in to add a comment