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

Issue 673596 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner:
Last visit > 30 days ago
Closed: Dec 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Regression



Sign in to add a comment

[UI] Network panel, when open should trigger a network scan every ~ 5-10 seconds.

Project Member Reported by aashuto...@chromium.org, Dec 13 2016

Issue description

Chrome Version: <From about:version: Google Chrome 56.0.2924.26>
Chrome OS Version: <From about:version: Platform 9000.26.0>
Chrome OS Platform: <Caroline>
Network info: <WiFi>

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

Steps To Reproduce:
(1) Click on the bottom left panel and then select a network.


Expected Result:
Network scan should trigger and show up as revolving blue ring (As in < M55 build)

Actual Result:
No  UI indicating scan.

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)
Always.

What is the impact to the user, and is there a workaround? If so, what is
it?
None. 

12290 2016-12-13T02:00:24.017237+00:00 DEBUG wpa_supplicant[841]: wlan0: nl80211: Scan trigger
  12291 2016-12-13T02:00:24.017253+00:00 DEBUG wpa_supplicant[841]: wlan0: Event SCAN_STARTED (47) received
  12292 2016-12-13T02:00:24.017267+00:00 DEBUG wpa_supplicant[841]: wlan0: Own scan request started a scan in 0.000109 seconds
  12293 2016-12-13T02:00:24.021106+00:00 DEBUG wpa_supplicant[841]: dbus: flush_object_timeout_handler: Timeout - sending changed properties of object /fi/w1/wpa_supplicant1/Interfaces/15


  11932 2016-12-13T02:00:14.017323+00:00 DEBUG wpa_supplicant[841]: wlan0: nl80211: Scan trigger
  11933 2016-12-13T02:00:14.017337+00:00 DEBUG wpa_supplicant[841]: wlan0: Event SCAN_STARTED (47) received
  11934 2016-12-13T02:00:14.017350+00:00 DEBUG wpa_supplicant[841]: wlan0: Own scan request started a scan in 0.000091 seconds
  11935 2016-12-13T02:00:14.021276+00:00 DEBUG wpa_supplicant[841]: dbus: flush_object_timeout_handler: Timeout - sending changed properties of object /fi/w1/wpa_supplicant1/Interfaces/15

I see scans getting triggered in the logs but UI does not reflect it. 


Please provide any additional information below. Attach a screenshot or
log if possible.

For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.


 
log-121216-181549.tar.gz
1.1 MB Download

Comment 1 by snanda@chromium.org, Dec 13 2016

Cc: yoshiat@chromium.org kirtika@chromium.org cernekee@chromium.org
Owner: steve...@chromium.org
Steven, I am assuming this falls on your plate given that this seems purely UI related.  Please redirect as appropriate.
I noticed this too and assumed it was intentional as part of the system menu UI redesign?
Cc: varkha@chromium.org
Owner: tdander...@chromium.org
Looking at chrome://device-log, we are sending RequestScan events, we just are not showing any spinner UI.

I don't know whether or not this is intentional, -> tdanderson@, cc: varkha@


Status: Available (was: Untriaged)
Mergedinto: 649799
Status: Duplicate (was: Available)
We have an OK to launch in m-56 without the infinite loader in the network detailed view. Merging this into issue 649799 where we still require clarification for the intended UX for m-57.

Sign in to add a comment