Issue metadata
Sign in to add a comment
|
Regression: ''Chrome Updates automatically to freshest version'' screen is seen struck after Sign-in to chrome page. |
||||||||||||||||||||||||
Issue descriptionVersion: 55.0.2878.0/8860.0.0 dev-channel Blaze,Daisy,Peppy OS: Chrome What steps will reproduce the problem? (1)Recover build>>Navigate to sign in to chrome overlay>>Leave sign in overlay idle for 5 to 7 secs and observe 'Chrome Updates automatically to freshest version'' screen (Please refer video) Note: If unable to re-pro issue during fresh installation check by power-washing the device and repeat step 1 Expected: 1.No such navigation to 'Chrome Updates automatically to freshest version'' screen should be seen after Sign in to chrome overlay. 2.If 'Chrome Updates automatically to freshest version'' screen is intended behavior then it should navigate back to sign in screen. Actual: 1.Instead 'Chrome Updates automatically to freshest version' screen is seen after sign in overlay. 2.Instead, page is seen struck at 'Chrome Updates automatically to freshest version' screen(Unable to proceed further until unless we click on browse as guest and exit guest mode then sign in overlay is seen). This is Regression issue as it is working fine in 53.0.2785.103/8530.81.0 stable-channel Jerry. @alemate: Please confirm the behavior.
,
Oct 4 2016
I saw the same issue on samus 8861.0.0. Network was pingable from VT2.
,
Nov 15 2016
Any update on this? This is marked as a 55 stable blocker, and we are nearing 55 stable.
,
Nov 28 2016
Any progress on this? We are nearing 55 stable and this is marked as a blocker, if we can get a fix in the next two days we can make the targeted RC, if not we may have to punt or delay.
,
Nov 29 2016
Is this still reproducible? I was unable to reproduce it using test images neither 55.0.2878.0/8860.0.0 no 55.0.2883.64/8872.64.0 . I also tried to recover clapper device in verified mode using latest 55.0.2883.64/8872.64.0 and got nothing unusual. Could you provide full scenario? 1) Are you using device in dev mode or in verified mode? 2) What image was installed prior to recovery?
,
Nov 29 2016
Unable to reproduce this issue in 56.0.2924.8/9000.9.0 Dev
,
Nov 29 2016
Ok, if this is not reproducible, please remove RBS. But if you have scenario to reproduce this for the initial version (55.0.2878.0/8860.0.0 ), please describe it, because this seems to be a race. This could be a timing issue with network detection (are you using WiFi connection, or wired?).
,
Dec 1 2016
Proactively removing RBS label, if we can repro, or we need a merge for this later please let me know.
,
Dec 1 2016
I am using WiFi connection. Issue is reproducible in initial version 55.0.2878.0/8860.0.0 dev channel peppy. Repro Steps: 1. Recover build via USB OR (Sign in to chrome and power-wash the device)>>And then navigate to sign in to chrome overlay. 2. Now leave sign in to chrome overlay idle for 1-3 minutes and Observe unnecessary navigation to 'Chrome Updates automatically to freshest version' screen .
,
Dec 5 2016
Moving this to M-57 as new OOBE is turned off for 55-56.
,
Apr 5 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by jbanavatu@chromium.org
, Oct 4 2016671 KB
671 KB Download