Issue metadata
Sign in to add a comment
|
Incorrect user data directory except explicitly configured in Group policy
Reported by
mdreyb...@gmail.com,
Mar 21 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.110 Safari/537.36 Steps to reproduce the problem: I face an issue during enterprise upgrade from Chrome 56.0.2924.76 to 57.0.2987.98. The issue reproduces also in 57.0.2987.110 Configuration: 1. Windows Server 2008 R2 2. Citrix XenApp 6.5 3. Chrome published User-related settings: 1. User account created CTest1.CTST08 2. Roaming profile configured, and redirected to \\fs001\USER_PROFILES_D\CTST08\Manager, Company\PROFILE 3. Group policy created to setup Chrome settings, but “Set user data directory” setting not configured What is the expected behavior? Chrome 56 was pointing to correct folder in D:\User_Profiles\, but v57 tries to load profile from incorrect C:\temp folder What went wrong? Load user profile from the same default folder as v56 Did this work before? Yes 56.0.2924.76 Chrome version: 57.0.2987.110 Channel: stable OS Version: Windows Server 2008 R2 Flash Version: Shockwave Flash 25.0 r0
,
Mar 21 2017
Hello mdreyband, Can you test on 58 beta and let us know if you see the same?
,
Mar 21 2017
I've installed v58.0.3029.19 from https://www.google.ru/chrome/browser/beta.html, it can't load any page right after installation, including chrome://version and chrome://about with error: "AW, Snap! Something went wrong while displaying this page." Can I try something else?
,
Mar 21 2017
We're NOT going to block M57 for this issue per group chat(blumberg@,georgesak@ and pbomanna@).
,
Mar 22 2017
Thanks you for reply. Can you confirm that you were able to reproduce this bug? Are there any workaround? Are there any other issues with other group policies?
,
Mar 23 2017
For the issue mentioned in #3, this is a known problem with Chrome and Citrix 6.5 (works fine in 7). We are currently working on fixing that, but no ETA yet. One workaround is to deploy the 32-bit version of Chrome, which should work. Can you try that instead? As for the original issue, is it still happening with 58 as well?
,
Mar 23 2017
The problem is related to 32-bit already, we've decided to remove 64-bit Chrome from our environment a while ago. As I mentioned before, I can't install 58 beta- it crashes right after start. Is it a correct link to download v58- https://www.google.ru/chrome/browser/beta.html?
,
Mar 23 2017
That looks like the correct link. Can you try with --allow-no-sandbox-job switch? This should not be needed on 58+, but was needed on 57 and previous. Just a sanity check to see if that's not the problem. If it still crashes, I'd like to double check your version in chrome://version. Obviously this won't be possible because of the crash so in that case, use --no-sandbox temporarily. But this is NOT a fix, as it greatly reduces the security. I can't stress this enough :)
,
Mar 28 2017
I've upgraded the browser today, chrome://version report is attached. I was able to start only using --no-sandbox switch, --allow-no-sandbox-jib switch doesn't helps me. Chrome.exe also crashes when I start it through Citrix published application, using --no-sandbox or without this.
,
Mar 28 2017
I've tried to restart in Citrix with other command line parameters- works fine, and profile points to correct folder. Looks like the issue was resolved in the latest beta version.
,
Apr 4 2017
@mdreyband-- Thanks for the update. Could you please check the same on latest stable and update the behavior. Thanks!
,
Apr 4 2017
@mdreyband If you can try Beta (M58) 32-bit instead of 64-bit, with no command line switches. It should just work (fingers crossed). If you can confirm that, it would be great. Link: https://www.google.com/chrome/browser/beta.html?platform=win Stable (M57) 32-bit should also work using --allow-no-sandbox-job. We are aware of an issue using Chrome 64-bit and Citrix 6.5 where the renderer will crash. Using --no-sandbox will allow it to work, but this is NOT a solution (that option is dangerous). This is currently under investigation. PS: I know this is diverging a bit from the original problem, but it's worth confirmation nonetheless, if you can. Thank you!
,
Apr 5 2017
A friendly reminder that M58 Stable launch is coming soon! Your bug is labelled as Stable ReleaseBlock, please make sure to land the fix, verified in trunk and get it merged into the release branch ASAP.
,
Apr 6 2017
A friendly reminder that M58 Stable is launch is coming soon (less than 2 weeks)! Your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and get it merged into the release branch ASAP so it gets enough baking time in Beta (before Stable promotion). Thank you!
,
Apr 13 2017
mdreyband@ as suggested in #12 would you mind trying with Chrome Beta 32 bit and update the thread. We will be promoting M58 to Pre-Stable next week (1% of Win users), is this still considered as a Stable Blocker?
,
Apr 17 2017
Can you please take a look at this urgently since this is marked as RB-Stable? We are aiming to launch M58 early stable this Wednesday, RC cut today @ 5:00 PM PT or latest by tomorrow noon if all goes well.
,
Apr 17 2017
Look like the issue is resolved, please escalate if needed.
,
May 2 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by gov...@chromium.org
, Mar 21 2017