Delays or unable to connect to network on Chrome 60 |
||||
Issue descriptionChrome Version: 9592.22.0 60.0.3112.34 OS:ChromeOs What steps will reproduce the problem? 1. Login to Chromebook 2. Wait until the network is connected 3. Connection fails 4. Wait for a while / connect to different network What is the expected result? The customer should be able to connect to the internet without delays or having to switch networks. What happens instead? The customer has to wait for a while or switch to a different network to connect to the internet properly. Date and Time of the issue reproduced: 2017/06/21 18:42 Using VPN and proxy network (Pac file). Customer has claimed that the issue started occurring after the Chrome updated to v.59. Before the update, he had no trouble connecting to the internet and all policies set were properly fetched when logged into the Chromebook. However, since several weeks ago, he has to wait for a while or switch to a different network to connect to the internet. The customer is using a proxy network (Pac file) when using a company-built VPN to connect to the internet. Debug logs & net-internal.json https://drive.google.com/open?id=0B01ZVp8vDQocbWUtR1g3SjZqTjA
,
Jun 30 2017
HW info: Model HP Chromebook 11 2200-2299 / HP Chromebook 11 G4/G4 EE Google Chrome Version 60.0.3112.50 Platform Version 9592.37.0 (Official Build) beta-channel kip Firmware Version Google_Kip.5216.227.78 Boot Mode Verified Enrollment Date Sep 15, 2015
,
Jul 7 2017
,
Jul 7 2017
,
Jul 7 2017
Which M59 update had this issue? Version number? Also, the fix is likely to land in M60 as M59 is nearing the last AU.
,
Jul 28 2017
Same problem observed in corporate environment here. Chrome tries to connect directly until second time pac file is obtained. Then it does start using it. This causes a delay for those who open Chrome by clicking on a link with Chrome initially closed, Chrome as default browser.
,
Jul 28 2017
Version 60.0.3112.78 (Official Build) (64-bit) on Windows 8.1 Problem is only when auto-detecting the pac file. not whenexplicitly configuring a pac file URL. Is there a fix for this or can I help triage this issue?
,
Dec 7
Hello! This bug is receiving this notice because there has been no acknowledgment of its existence in quite a bit of time - If you are currently working on this bug, please provide an update. - If you are currently affected by this bug, please update with your current symptoms and relevant logs. If there has been no updates provided by EOD Wednesday, 12/12/18 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary. Thank you!
,
Dec 13
Due to lack of action this bug has been Archived. If work is still being done on this issue or you are still experiencing this issue please feel free to re-open with the appropriate information. |
||||
►
Sign in to add a comment |
||||
Comment 1 by marcore@chromium.org
, Jun 28 2017