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

Issue 689855 link

Starred by 5 users

Issue metadata

Status: WontFix
Owner:
Closed: Mar 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression : Unable to connect to Wi-Fi for first time in OOBE screen

Project Member Reported by mmanchala@chromium.org, Feb 8 2017

Issue description

Chrome Version: 58.0.3001.0/9261.0.0 dev-channel Glimmer, Zako, Panther
OS: Chrome

What steps will reproduce the problem?
(1)Recover build -> In OOBE screen Click on "Let's go" so that "Connect to Network" screen is seen
(2)Now try to connect to Wi-Fi network and observe network is not connected(Please refer video)

Expected: Should be able to connect to Wi-Fi immediately after entering correct password 
Actual: Instead Unable to connect to Wi-Fi for first time 

Note: 
1. Able to connect to selected Wi-Fi Network after entering password for 6-7 times 
2.'Network Connection Error' notification is also not seen when wrong password is entered

This is Regression issue as same is working fine in 58.0.2998.0/9247.0.0 dev-channel Glimmer

@alemate :  Please confirm the issue
 
Actual_UnableToConnect.mp4
8.5 MB View Download
Attaching Expected video
Expected_ConnectingToWi-Fi.mp4
5.6 MB View Download

Comment 2 by ajha@chromium.org, Feb 8 2017

Cc: vsu...@chromium.org pucchakayala@chromium.org
Cc: cernekee@chromium.org
Labels: -ReleaseBlock-Dev ReleaseBlock-Stable
+cernekee

Do we have logs from any of these failures?

If this is OOBE only we may not want to bother blocking Dev on it, no Dev channel recovery images go out to the public so OOBE there is not going to be that common.
Can we confirm whether this is different from  bug 689795 ?
Owner: mmanchala@chromium.org
mmanchala, could you check if this is still reproducible?
The issue cernekee@ pointed to, seems related.
Cc: alemate@chromium.org
Owner: alemate@chromium.org
As per comment # 6 checked Issue in 59.0.3041.0/9389.0.0 dev-channel Peppy Build and unable to repro the issue.
Status: WontFix (was: Assigned)
Closing as unreproducible.

Sign in to add a comment