bzub/20180819-crostini_sommelier_fix.md

Last active January 24, 2024 12:15

Star () You must be signed in to star a gist
Fork () You must be signed in to fork a gist

Learn more about clone URLs
Clone this repository at <script src="https://gist.github.com/bzub/65aabace4a60874c61ece4838b6219f3.js"></script>
Save bzub/65aabace4a60874c61ece4838b6219f3 to your computer and use it in GitHub Desktop.

Download ZIP

Fix Crostini Wayland/X (sommelier) service

Raw

20180819-crostini_sommelier_fix.md

If you can't get X11 or Wayland GUI Linux apps to start anymore on Chrome OS, try the following.

In the Terminal app, this will show the status of your systemd user services/units:

systemctl --user

If [email protected] and [email protected] show a failed status, the following worked for me:

sudo ln -s /opt/google/cros-containers/bin/sommelier.elf /usr/bin/
systemctl --user restart [email protected]
systemctl --user restart [email protected]
export DISPLAY=:0

Check again to see if those services are started now:

systemctl --user

Hopefully now X/Wayland apps work again.

xclock

dimpase commented Aug 27, 2018

@jpelton-stroud - I also did see this, and some reboots fixed it.

I think chrome launcher for x11/wayland apps is currently broken, and trying to use it actually leads to this error on the container. Not using it, but just the terminal, to start x11/wayland apps does work.

Lucaacer commented Sep 2, 2018

It seems that both services are running on my Lenovo Pyro, but I will make a further check.

[email protected] loaded active running X11 sommelier at display 0
[email protected] loaded active running Master sommelier listening on socket wayland-0

Thanks for the hint.