Chrome fails to run as Citrix Streamed App |
|||||
Issue description
We both deploy to Citrix-delivered desktops and Citrix-stream Google Chrome v53 but need to upgrade for security patching compliance.
I started with v55 (which failed) but days later v56.0.2924.76 was released so I tried that as well - still failed.
Now v56.0.2924.87 is out and I've tried that as well, all to no avail.
Symptoms
All versions successfully deploy as installed applications on Citrix virtualised desktops but when packaged to be delivered as a Citrix Streamed application (to standard Windows desktops) Google loads as a frame but with an entirely blank (black) screen and no ability to access any functions such as settings.
By direct-accessing the server where Google is deployed for streaming, it is possible to successfully load it directly from the install share - it is only as a virtualised stream that is it failing to load at a client PC.
After attempting many suggestions from this and other forums, we have identified that we can run the stream by specifying the --no-sandbox switch
(NOTE: the --allow-no-sandbox-job switch which SHOULD permit a Citrix streaming to work, appears to have no beneficial effect)
Unfortunately the --no-sandbox switch is boldly stated to be unsupported by Google and that it WILL result in application security and Stability failures.
We have tried:
Different profilers
Different Citrix streaming servers
Profiling both the 32bit and 64bit MSI's
(unsurprisingly the 32bit version failed to deploy on the 64bit streaming server)
Three different versions of the MSI
We are streaming using Citrix XENAP version 6.5 and use the Citrix streaming profiler v6.7
We are using the latest Google enterprise .MSI - googlechromestandaloneenterprise64.msi
We are successfully deploying to Windows 7 Citrix Desktops (both 64bit and 32bit)
We can directly access and load the profiled 64bit stream-source deployed on hosting Windows 2K8 Citrix servers but ... CANNOT access the streamed 64bit source from those Windows 2K8 servers.
,
Mar 14 2017
,
Mar 16 2017
Xenapp 6.5 w/ Chrome 55+ is exhibiting this behavior. Xenapp 7.x does not have this issue. We are actively investigating this issue.
,
Mar 16 2017
I have a client experiencing the same issue but also on both published application and Citrix Desktop. while in regular(sandbox) mode for users: no webpages load, they can't access chrome internal pages like settings. - the server was infected but was cleaned with Malwarebytes - Citrix Xenap 6.0 - Google Chrome: started with version 55 updated to 56 and now on 57.0.2987.98 - only works in -no-sandbox mode for users - administrator account works fine in and out of sandbox mode - have also tried various chrome versions, complete removal and reinstall - OS: Windows Server 2008 R2 SP1 Enterprise 64-bit
,
Mar 24 2017
@4 I'm looking more actively into this issue. Do you mind testing the 32-bit version of 57 with --allow-no-sandbox-job switch? Thanks.
,
Mar 26 2017
Hi George - I shall download, package, deploy and test as early as I can this week. Can I also confirm that this version of Chrome will have TLS 1.3 removed from it after the fiasco with the likes of Blue Coat (proxy) not supporting the current build of TLS1.3? Thank you Col. S
,
Apr 5 2017
Ping - any updates on this issue?
,
Apr 5 2017
HI v57 gone through discovery and change control and is with the packaging team now. Expect it to be packaged tomorrow (Thurs 6 Apr) or Fri 7 Apr for QA and UAT testing sometime Friday at the latest. Thank you for your patience From: ko… via monorail [mailto:monorail+v2.1549364410@chromium.org] Sent: Wednesday, 5 April 2017 4:13 PM To: affiliate@techtamed.com Subject: Issue 699043 in chromium: Chrome fails to run as Citrix Streamed App Comment #7 on issue 699043 by kotah@chromium.org <mailto:kotah@chromium.org> : Chrome fails to run as Citrix Streamed App https://bugs.chromium.org/p/chromium/issues/detail?id=699043#c7 Ping - any updates on this issue?
,
Apr 6 2017
Hi team Thank you for your support. I'm sorry to report that the issue is unresolved and apparently unchanged by using the latest MSI of Chrome - 57.0.2987.133 Copyright 2011 Google Inc. Exactly the same response when packaged and streamed with the blank browser frame with an X in the tab title an no ability to perform ANY action including in-built functions such as Help-About or Settings, ... although ... as I type this I realise I did not confirm with the packager if he had tried it with the --allow-no-sandbox-job switch. Please let me confirm with him tomorrow and I will report back.
,
Apr 7 2017
I'm sorry to report that 57.0.2987.133 (32bit) is still inoperative as a Citrix stream even when used with --allow-no-sandbox-job switch. The *only* way to make it work is to use the --no-sandbox switch! Just to confirm the parameters Streaming from ZenApp v6.5 ZenApp running on Win 2k8r2 Chrome failure images attached
,
Apr 10 2017
This is an FYI comment. Not wanting to confuse the issue but some more observations to-hand. I wanted to verify v56 was actually working when "deployed" to provisioned Citrix desktops (as opposed to failing when streamed to pooled LMG desktops). I used Remote Desktop to access one such "provisioned" Citrix desktop VM using my Admin (A) account and ran v56 successfully but due to Admin browse restrictions I could not load web sites so I did a RUNAS using my general User (U) account [from within my A account] and discovered this resulted in the "Broken Chrome" scenario! (No settings/help etc, nothing but the blank frames) I could not RDP that Citrix desktop with my U account due to security restrictions so I set up my Citrix access so that I could directly logon to that desktop with my U credentials. Under that scenario Chrome v56 does work ok as a deployed app. My point is that RDP to a Citrix VM as a Local Admin saw Chrome work yet then using RUNAS to load Chrome with standard user rights caused it to break even as a deployed application ... yet logging in directly as a standard user the deployed version works. So does that indicate a rights issue breaks Chrome (when streamed) or is it that RUNAS introduces an additional layer of abstraction (sandboxing?) which is causing the failure. As I said - this is just an FYI comment in-case it helps resolve the Citrix streaming failure being addressed in v57. (So I do not expect a response to this comment) Regards Col. Sanders
,
Apr 13 2017
I think this is caused by the same root cause as a few other issues with Chrome on Citrix 6.5. Please read https://bugs.chromium.org/p/chromium/issues/detail?id=432595#c15 and try if this fix helps in your case too and I will close this issue if this is the case.
,
May 10 2017
pastarmovj@ assigning to you in case you have any updates and this can be closed.
,
May 11 2017
I think we can close this, one of the affected customers already confirmed #c12 resolved the issue. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by kotah@chromium.org
, Mar 14 2017Labels: Hotlist-Enterprise