New issue
Advanced search Search tips

Issue 919699 link

Starred by 3 users

Issue metadata

Status: Verified
Owner:
Closed: Jan 8
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Crostini: Error installing/opening crostini

Project Member Reported by avkodipelli@chromium.org, Jan 8

Issue description

Chrome Version: 73.0.3664.0
Chrome OS Version: 11541.0.0
Chrome OS Platform: Kevein, sona
Network info: Wifi

Please specify Cr-* of the system to which this bug/feature applies (add
the label below).

Steps To Reproduce:
(1) Goto chrome setting and install Linux/crostini 
(2) Or open existing terminal after auto update to above version.
(3) Observe behavior.

Expected Result:
- Terminal opens or Linux installs without any issues.

Actual Result:
- Unable to open terminal or unable to do fresh installation of Linux.

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)
Always

Feedback report: https://listnr.corp.google.com/report/85893698961
 
Cc: smbar...@chromium.org
Dev is coming soon, please assign owner and prioritize resolution accordingly. 
Owner: smbar...@chromium.org
Status: Assigned (was: Untriaged)
smbarber, please take a look. This is on 4.4 so it's probably not the vsock failure.
Labels: -ReleaseBlock-Dev
tast.vm.StartCrosvm is passing in lab. Stainless results: https://stainless.corp.google.com/search?view=matrix&row=board&col=build&first_date=2019-01-06&last_date=2019-01-08&test=tast.vm.StartCrosvm&exclude_cts=true&exclude_not_run=false&exclude_non_release=true&exclude_au=true&exclude_acts=true&exclude_retried=true&exclude_non_production=false

Manually also verified it is working on the above build. 
Looks like component update from 11316.7.0 to 11542.0.0 has fixed the issue.
Removing Dev blocker and dev can close the issue if nothing else is there to fix. Thanks!
Status: Fixed (was: Assigned)
Yes this is also looking okay for me. There was a bad component push due to a broken imageloader manifest (11540.0.0). We followed up with 11542.0.0 which resolved the issue.
Status: Verified (was: Fixed)
Closing the issue as per #5 comment.

Sign in to add a comment