Acer Chromebook 14 and Acer Chromebox do not wake up from sleep |
|||
Issue descriptionChromeOS version: 65.0.3325.209 ChromeOS device model: Acer Chromebook 14 (Lars), Acer Chromebox Case#: 15574989 Description: The power button (or any other keys pressed) do not wake the device. The screen remains black and the device will not wake/boot at all, despite having full charge and being connected to a power source. The only solution is to start the recovery process, then reboot the device without recovering a device. Sometimes the login/password screen is shown, but the mouse and keyboard (internal and external USB keyboard/mouse) do not respond. The only solution is to be to reboot the device. This never happens while a regular use and only occurs when the device is being woken from sleep. A full reset/recovery of device device does not seem to make any difference. These two issues are occurring on both Acer Chromebook 14 and Acer Chromebox devices. The issue is intermittent and is not easily reproducible. Drive link to logs: https://drive.google.com/open?id=10_MJ49zgouu7gGg5xIc80v_sDQv6FtxX Latest crash IDs: 2018-04-03 - 6222882492b0cbed 2018-04-04 - 9db8ae1d45b653d6 2018-04-04 - b07c21d97967c660 2018-04-04 - 01e7806108e7d2a5 2018-04-05 - 737dd301fff58c04 2018-04-10 - 8b10d838689f220b 2018-04-20 - 796124d0eac24c96 ### Additional information ### After updating to a beta version - 67, devise shows a bit different symptoms. After the boot of device and login, the screen goes black briefly and then display returned and user is able to log in. They have a dialogue box in Chrome saying something went wrong and chrome window did not shut down properly. The screen resolution within Chrome also gets wrong. Debug logs from Beta: https://drive.google.com/open?id=16_DFnn57--nxFsEs-kdJSKNs6UVscLj_ Crash ids from Beta: b2bfcd59ab73dd2d c15b60f4aecf0c3d 455df084b77466cd From crash id in Beta logs, it might be related to https://bugs.chromium.org/p/chromium/issues/detail?id=836119
,
Jun 1 2018
moving to platform for triage
,
Dec 7
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/12/18 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary. Thank you!
,
Dec 13
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 ovanieva@chromium.org
, May 18 2018Owner: omrilio@chromium.org
Status: Assigned (was: Untriaged)