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

Issue 732480 link

Starred by 1 user
Status: WontFix
Owner:
pastarmovj@chromium.org
Closed: Aug 2017
Cc:
█ abdulsyed@chromium.org
pbomm...@chromium.org
georgesak@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Legacy Browser 4.7 not loading under 59.0.3071.86

Reported by dcstokes@gmail.com, Jun 12 2017 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.86 Safari/537.36

Steps to reproduce the problem:
1. set the Chrome GPO "set user data directory" setting
2. LBS 4.7 64 bit
3. Version 59.0.3071.86 (Official Build) (64-bit)

What is the expected behavior?
redirected corporate intranet sites that are not compatible with chrome redirect to IE 11 using legacy browser extension

What went wrong?
LBS failed on loading or screen hangs white stopping usage
need to delete either 
C:\Users\user\AppData\local\Google\Chrome\User Data\Default\Managed Extension Settings\heildphpnddilhkemkielfhnkaagiabh or delete chrome user profile to recreate

Did this work before? Yes 55.0.2883

Chrome version: 59.0.3071.86  Channel: stable
OS Version: 7 -10
Flash Version: 

Working fine before on other versions but has manifested on 59.0.3071.86 we set the user directory to enable shared usage on rup and roaming profiles similar to  Issue 307087

Comment 1 Deleted

Comment 2 by pbomm...@chromium.org, Jun 12 2017

Cc: -ligim...@chromium.org pbomm...@chromium.org abdulsyed@chromium.org georgesak@chromium.org
Labels: pre-stable-59.0.3071.86 M-59
Owner: pastarmovj@chromium.org
Status: Assigned (was: Unconfirmed)

Comment 3 by pastarmovj@chromium.org, Jun 13 2017 

I don't think this is particularly related to LBS rather to Chrome running with a profile on a network share. If this is the case I should not that this has never been fully supported and since Chrome 58 seems to have stopped working unless the browser is ran without its sandbox which is a really bad idea. One mitigation is to use a locally mounted as drive share or even better keep the profiles in their default not roamed location and enable the newly introduced roaming profile support in Chrome as described here https://support.google.com/chrome/a/answer/7349337?hl=en 

If you only observe the issue with LBS when transitioning to IE please upload screenshots of the issue.

Comment 4 by dcstokes@gmail.com, Jun 13 2017 

OK I noticed last night the new roaming profile support policies and that the amdx templates had changed I'll test these as currently my policies are set to

Set disk cache directory Enabled  
Set disk cache directory ${local_app_data}\Google\Chrome\User Data 
 
Set user data directory Enabled  
Set user data directory ${roaming_app_data}\Google\Chrome\User Data 

I'll attach screen grabs if I can but am on training currently

Comment 5 by dcstokes@gmail.com, Jun 15 2017

Capture1.jpg
37.7 KB View Download

Comment 6 by pastarmovj@chromium.org, Jun 15 2017 

Thanks. Is it possible to press F12 while on this white tab to open the developer tools and the error list or is the complete browser hung. If it is possible. Please take another screenshot with it open.

Comment 7 by pastarmovj@chromium.org, Aug 29 2017 

Friendly ping! 

Can you please provide the info requested in c#6?

Comment 8 by dcstokes@gmail.com, Aug 29 2017 

There was nothing in the logs suggesting a problem with the extension or chrome. The resolution was more to do with a corrupt GPO on our side which restoring fixed this.

Please close the ticket

Regards

Comment 9 by pastarmovj@chromium.org, Aug 29 2017

Status: WontFix (was: Assigned)
Thanks for the feedback!
►

Sign in to add a comment