Skip to content

Instantly share code, notes, and snippets.

@bzub

bzub/20180819-crostini_sommelier_fix.md

Last active September 9, 2022 19:34
  • Star 17 You must be signed in to star a gist
  • Fork 1 You must be signed in to fork a gist
Star You must be signed in to star a gist
Embed
What would you like to do?
Learn more about clone URLs
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 sommelier@0.service and sommelier-x@0.service show a failed status, the following worked for me:

sudo ln -s /opt/google/cros-containers/bin/sommelier.elf /usr/bin/
systemctl --user restart sommelier@0.service
systemctl --user restart sommelier-x@0.service
export DISPLAY=:0

Check again to see if those services are started now:

systemctl --user

Hopefully now X/Wayland apps work again.

xclock
@williamwilkerson2
Copy link

How to disable X Wayland and enable X Org on Crostini?

@vdegenne
Copy link

vdegenne commented Dec 29, 2020 •
edited

You are such a genius... Thanks a tone !
Has this issue been reported to the Chrome OS team by the way? Seems like a bug after all.

@TheTechRobo
Copy link

Thank you very much! This worked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment