Sometimes network not available dialog blocks sign-in even though network is connected |
||||||||||||||
Issue descriptionChrome Version: M61.0.3159.0 dev peach-pit OS: ChromeOS 9756.0.0 What steps will reproduce the problem? (1) On newly recovered device or one that has been wiped via clear tpm, enroll device to domain. (2) Proceed through OOBE. What is the expected result? After the completion of enrollment, sign-in screen is presented. Even if network is not connected, it can be successfully connected manually and advanced to the sign-in screen. What happens instead? After enrollment, the "Network not available" dialog is presented. No network is connected. A network can be successfully connected manually from the lower right network icon in the tray. However, the screen would not advance to the sign-in screen. Select a working network from the drop-down list in the "Network not available" dialog does nothing. To get out of this state, one needs to Browse as a guest or click the "sign in as an existing user" link at the bottom of the dialog or reboot the device. I believe this is basically network UI issue. This issue was only seen intermittently during the course of testing on peach-pit and auron-yuna. When this happened, via VT2, it was confirmed network was working normally and wget was able to retrieve web content from websites.
,
Jul 21 2017
Saw again on M61.0.3162.0:9765.0.0 dev kevin after finishing enrollment asset name/location dialog and before the sign-in screen. Even changing network selection and selected, the network dialog remained and showed Network not available.
,
Aug 11 2017
,
Aug 11 2017
,
Aug 11 2017
,
Aug 11 2017
,
Aug 11 2017
Is it reproducible on M-60? If not, why are we blocking stable M-60?
,
Aug 11 2017
Yes it's happening in today's M60 too.Jing will be adding proper steps to repro this. M ChromeOS Chrome ARC Type Channel 60 9592.82.0 60.0.3112.101 (multiple) release stable
,
Aug 11 2017
How consistently this is happening? Also, was this present in previous M60 Stable build? Steven/albert, can you help debugging this issue?
,
Aug 11 2017
We do see it couple of times but it's not consistent every time.
,
Aug 11 2017
Pulling off RB-Stable, but we should find someone to look at this since it reproduces easily.
,
Aug 15 2017
This is a problem with the "network not available" UI. It should use the chrome.networkingPrivate API to identify when a network is connected and close the dialog (or do whatever is appropriate). We should probably plan to fix this when we address issue 689198 ; assigning to wzang@.
,
Aug 15 2017
Removing M-60 label and re-prioritizing since this doesn't seem to be occurring regularly?
,
Aug 15 2017
This can be addressed together with the network error screen update, but please note the update won't make M61 though. Both issues need to be punted.
,
Aug 16 2017
,
Aug 16 2017
,
Aug 16 2017
,
Sep 15 2017
,
Sep 16 2017
I just checked this issue and it seems to be the same as issue 756364.
,
Sep 16 2017
Or may be it is hidden behind issue 756364.
,
Oct 3 2017
|
||||||||||||||
►
Sign in to add a comment |
||||||||||||||
Comment 1 by aashuto...@chromium.org
, Jul 19 2017