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

Issue 808103 link

Starred by 1 user
Status: WontFix
Owner:
za...@chromium.org
Closed: Feb 2018
Cc:
chirantan@chromium.org
smbar...@chromium.org
dgreid@chromium.org
█ reve...@chromium.org
tbuck...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Graphical Linux apps not working

Project Member Reported by tbuck...@chromium.org, Feb 1 2018 
Chrome version: 66.0.3329.0 canary
OS: Chrome

Repro steps:
1. Start a container: go/debian-on-cros
2. Try to launch a graphical app, eg. VS Code or emacs

Expected: app window opens
Actual: no app window opens; emacs falls back to terminal version

Comment 1 by reve...@chromium.org, Feb 1 2018 

Not limited to graphical apps as the basic weston-info utility is also failing. Seems like wayland connections are failing without any error messages.

Comment 2 by za...@chromium.org, Feb 1 2018 

It was a permission issue with crosvm not having the wayland gid. Because of that, crosvm could not open wayland-0 on the host.

Comment 3 by za...@chromium.org, Feb 5 2018

Cc: chirantan@chromium.org smbar...@chromium.org
The fix for this is predicated on the merging of the "concierge" VM launching daemon, which will give crosvm the proper supplementary permissions, as I understand it. smbarber@, chirantan@, or dgreid@ have more info on the progress of that.

Comment 4 by smbar...@chromium.org, Feb 15 2018

Status: WontFix (was: Assigned)
The underlying permission issue was fixed with the switch to concierge. With a hacked together debian lxd container, wayland works again.

Comment 5 by vapier@chromium.org, May 17 2018

Labels: -Restrict-View-Google
►

Sign in to add a comment