New issue
Advanced search Search tips

Issue 781048 link

Starred by 1 user
Status: Closed
Owner:
r...@chromium.org
Closed: Dec 10
Cc:
abodenha@chromium.org
weifangsun@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Unable to login from OOBE flow on M64 canary

Project Member Reported by weifangsun@chromium.org, Nov 2 2017 

Updated my canary device to the latest version today (64.0.3254.0) and am unable to complete the initial OOBE workflow (had to reset my device for TPM update).

Feedback report here for reference -
 https://listnr.corp.google.com/report/80764418352. (could just be temporary issue with canary build)

Comment 1 by apronin@chromium.org, Nov 3 2017 

The question is why did the device go back to OOBE. Based on what I see in the logs, the TPM was still owned when it booted after that update, but looks like the stateful was wiped and it caused OOBE workflow.

Comment 2 by apronin@chromium.org, Oct 12

Components: OS>Systems>Security

Comment 3 by louiscollard@chromium.org, Dec 10

Status: Closed
Seems like a single instance on a now very old build - closing

Comment 4 by louiscollard@chromium.org, Dec 10

Status: Closed
Seems like a single instance on a now very old build - closing
►

Sign in to add a comment