[Tiger|Fievel] Unable to install ARC applications |
||||||||||||
Issue descriptionChrome Version: 66.0.3359.35 Chrome OS Version: 10452.14.0 Chrome OS Platform: Veyron Tiger - Veyron Fievel Network info: GoogleGuest Please specify Cr-* of the system to which this bug/feature applies (add the label below). Steps To Reproduce: (1)Enroll Device in a OU which has ARC applications (2)Configure OU to auto launch ARC application, or manual launch (3)Attempt to initialize application Expected Result: Application should install and launch after a couple of minutes Actual Result: Chrome OS device hangs in "Initializing application window" How frequently does this problem reproduce? (Always, sometimes, hard to reproduce?) Always What is the impact to the user, and is there a workaround? If so, what is it? User wont be able to execute ARC ++ applications, upgrading to ToT M67 Please provide any additional information below. Attach a screen shot or log if possible. I tried to auto launch and manual launch a couple of ARC applications, once the application is initialized, the device gets stuck in "Initializing application window" screen. I also tested on M67 ToT (10494.0.0 67.0.3369.0) and the fix works fine, applications are initialized and are working properly. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Mar 26 2018
is this a blocker for M66 stable ? looks like it works in M67 ?
,
Mar 26 2018
original discussion can be found here https://bugs.chromium.org/p/chromium/issues/detail?id=811398
,
Mar 28 2018
,
Mar 28 2018
,
Mar 28 2018
,
Mar 28 2018
,
Mar 28 2018
@shubhar, Does this qualify as a Release block Beta or a Release Block Stable for M66?
,
Mar 28 2018
Updating this to Release Block Stable. Please change Priority/status, if you feel otherwise
,
Mar 28 2018
,
Mar 28 2018
only affects two kiosk devices, Tiger and Fievel
,
Mar 28 2018
,
Mar 28 2018
I had a conversation with sergey offline a couple of days ago. He mentioned that the problem is happening with Cloud DPC. This bug does not present itself on M67 ToT.
,
Mar 29 2018
It should be fixed from M66-10452.30.0. It was duplicate of http://b/74098558
,
Mar 29 2018
[Auto-generated comment by a script] We noticed that this issue is targeted for M-66; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-66 label, otherwise remove Merge-TBD label. Thanks.
,
Apr 4 2018
Verified using Tiger 10452.44.0
,
Apr 5 2018
,
May 17 2018
|
||||||||||||
►
Sign in to add a comment |
||||||||||||
Comment 1 by vaandres@chromium.org
, Mar 26 2018