Chromebook OS 69 with SAP PM UI5 app no longer works. |
||
Issue descriptionChromeOS version: 69.0.3497.73 ChromeOS device model: Caroline (Samsung Chromebook Pro) Case#: 16904820 Description: Chromebook OS 69 with SAP PM UI5 app no longer works. Customer has reported that they have been experiencing some issues to rum SAP PM UI5 apps. Please refer the attached vide files. https://drive.google.com/open?id=1Eo_3MNn299trh2lznLzoL3vz9vHxAAS7 https://drive.google.com/open?id=1lgrHEyrkW-Lf8HmCksXI2Os8WL5Pn45n Current Behavior / Reproduction: The error message appears when click WEB like (Work Order Execution) on the Browser and SAP PM UI5 app doesn’t start. Expected Behavior: SAP PM UI5 apps should open without error. - All troubleshooting steps already taken: a) Wiped the device and the issue persists. b) Chrome OS version 65 doesn’t reproduce the issue. c) verified a different network and the results are the same. d) Confirmed Windows and Mac were working as expected. - Time/date the issue first occurred: the problem started when the Chromebooks were updated to version 69. Drive link to logs: Device log file. https://drive.google.com/open?id=1sAu8qzj1nFg6kmZ4tBHJqii3lcwJfYQt ((Debug logs were generated on 09/17/2018 and the issue was reproducible around 11:00 to 11:30 EST) .Har file. https://drive.google.com/open?id=1ztCSI2NsYzW-Fms3XD3ihKHI7kmsUe0N Policy json file. https://drive.google.com/open?id=1YAQniF4e1ys9oKVJG0yEXrb_zepQcaZO Crash reports https://drive.google.com/open?id=1yNsiGJuwtEKwnQVbql1Msy5033ghEv_H User domain info. https://drive.google.com/open?id=1RQiKm4aFV-zYWNfFA8ni4fgtwP1n9oPFnCFtpfeoDzQ Screen shot. Chrome:version: https://drive.google.com/open?id=1pLj26oLoADxd6Xo-R1Gk1zIKWWsVf0tX Browser info: https://drive.google.com/open?id=1fx2cvYHIBU-vuBnE60Sy8jOHL86B4-EU .Har error message: https://drive.google.com/open?id=1SeF_8J53sZofEHEZVbaWgWvcCLjK52rT .Har Headers info: https://drive.google.com/open?id=1G-Kg3Z6NKEMn_w83jd0GM0JYPNzGxmO5 Policy: https://drive.google.com/open?id=1MUP7A6dkvb0EdCcH-m_y8SIPLwt-AsKa
,
Dec 14
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/19/18 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary. Thank you!
,
Dec 20
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
, Sep 20