New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 690692 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner:
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Hotrod app not launching on CFM guado's (latest M56 production beta)

Project Member Reported by harpreet@chromium.org, Feb 9 2017

Issue description

We have few guado's in the lab that are on production beta channel (current build: 9000.82.0 / 56.0.2924.87) these are enrolled in CFM but are not able to launch the hotrod app after reboot. These devices are in dev mode.

After reboot, press ctrl + d on the OS verification screen to get past this screen, Chrome start up screen flashes for a quick second before proceeding to kiosk app trying to launch with 'Chrome' logo instead of the expected hangouts app logo. 'Press ctrl+alt+s to switch to Chrome OS' message is also shown at the bottom of the screen when the app tries to launch. Within couple seconds the screen goes blank and stays that way.

At this point, I am able to go to VT2 and run any shell commands but I am not able to return to the UI. Even restarting UI does not help.

Attaching a video of the boot sequence as well as the logs from the device.
 
I think we are seeing issue 664659. SSD is probably filled up.

There are also a few huge chrome logs under /var/log/chrome. If you remove them, you might get it back to work.
Glad we're catching this now. 
Mergedinto: 664659
Status: Duplicate (was: Untriaged)

Sign in to add a comment