New issue
Advanced search Search tips

Issue 901599 link

Starred by 7 users

Issue metadata

Status: Fixed
Owner: ----
Closed: Nov 15
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

vsh into termina fails always

Reported by kemper.m...@gmail.com, Nov 3

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS aarch64 11210.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3593.0 Safari/537.36
Platform: 11210.0.0 (Official Build) dev-channel elm

Steps to reproduce the problem:
1. Activate crostini
2. Open crosh
3. vsh termina

What is the expected behavior?
A shell in the termina vm opens and i can manage containers

What went wrong?
Several errror messages appear:
Most of the time:
crosh> vsh termina
[ERROR:utils.cc(50)] Failed to read message size from socket: Resource temporarily unavailable
[ERROR:vsh_client.cc(121)] Failed to receive response from vshd

Sometimes:
crosh> vsh termina
[ERROR:vsh.cc(324)] Failed to connect to vshd: Connection timed out

It never works.

vsh termina penguin 
works

Did this work before? N/A 

Chrome version: 72.0.3593.0  Channel: dev
OS Version: 11210.0.0
Flash Version: n.a.
 
same type of error

error continues after

vmc destroy termina
vmc start termina

flipping the switch on and off in the settings, "Remove Linux apps for Chromebook"

powerwashing chromebook.

This is on a 71.0.3578.27 beta  On a Samsung Kevin

further info,  for me OP's command
vsh termina penguin         ** did not work.

But penguin works from the launcher.
Screenshot 2018-11-03 at 4.57.21 PM.png
128 KB View Download
Screenshot 2018-11-03 at 5.01.41 PM.png
26.9 KB View Download
Components: OS>Systems>Containers
Todays update of the termnina component to 
cros-termina - Version: 11220.0.0
seems to have fixed it for me.

Great, when will this hit beta?
Or is there a way to update to it manually? I tried going into chrome://components and updating, but it doesn't do anything.

After I hit "Check for update" I just get:

cros-termina - Version: 11151.4.0
Status - Component not updated
Status: Fixed (was: Unconfirmed)
Has anyone on the Beta channel gotten this fix yet? I've gotten 2 ChromeOS updates since I first started seeing this issue, but this issue still isn't fixed.

Normally I would just wipe this thing and start over, but there's 1 file I need out of my Linux VM.
Nope, I've had 2 updates too and I've wiped my vm but it still doesn't work.

Sign in to add a comment