Arch Linux User Repository

sommelier-x unable to start

-- The job identifier is 472.
Jun 20 08:23:12 penguin sommelier[380]: MESA-LOADER: failed to open virtio_gpu (search paths /usr/lib64/dri)
Jun 20 08:23:12 penguin sommelier[380]: failed to load driver: virtio_gpu
Jun 20 08:23:12 penguin sommelier[380]: MESA-LOADER: failed to open kms_swrast (search paths /usr/lib64/dri)
Jun 20 08:23:12 penguin sommelier[380]: failed to load driver: kms_swrast
Jun 20 08:23:12 penguin sommelier[380]: MESA-LOADER: failed to open swrast (search paths /usr/lib64/dri)
Jun 20 08:23:12 penguin sommelier[380]: failed to load swrast driver
Jun 20 08:23:12 penguin sommelier[380]: error: couldn't get display device
Jun 20 08:23:12 penguin systemd[59]: sommelier-x@0.service: Main process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel

In-order to resolve:

 sudo pacman -S xwayland xorg-server-xwayland
 sudo cp /usr/lib64/dri/swrast_dri.so /usr/lib64/dri/swrast_dri.so.backup
 sudo cp /opt/google/cros-containers/lib/swrast_dri.so /usr/lib64/dri/swrast_dri.so
 systemctl --user restart sommelier-x@0.service

Just pushed an update which should fix xxd dependency issue and also "Linux Files" with recent systemd (thanks @kitakar5525 for investigation). Please report any other issues you see.

I am currently looking into making GPU acceleration work with Arch.

Garcon seems incompatible with systemd 242.19-1

When I tried to mount Linux files on the Files app, I got the following error:

$ tail -f /var/log/messages
2019-05-29T08:29:17.169951+09:00 ERR vm_cicerone[6721]: Failed to set up user: failed to enable linger: Could not enable linger: Read-only file system

It seems that our issue is related to this systemd issue: - loginctl enable/disable-linger error: read-only file system · Issue #12401 · systemd/systemd

As suggested in the above issue, adding ReadWritePaths=/etc /run /var/lib/systemd/linger to /usr/lib/systemd/system/systemd-logind.service worked as a workaround for our issue, too.

(Sorry I removed my previous comment by mistake.)

Garcon seems incompatible with systemd 242.19-1. Downgrading systemd to 241.93-1 fixes Chrome OS Files integration and launching from the Terminal app.

I had to downgrade systemd to version 241.7-2 in order to get garcon to work again.

Hello. First of all thanks a lot for the package!

I have the same problem with @uncon. I can't seem to run vim after updating to the latest release, because of "unresolvable package conflicts" with xxd-standalone. Anyone know how to work around this?

On chromeos 75.0.3753.0, i had to change pkgver to r134.7dac7e9 and remove xxd-standalone from depends to get it up & running.

@nickpelone, I noticed same as well, don't have time to identify the root cause of the issue yet. Another issue with arch container is there is no way to use graphics accelerarion yet, due to old glibc version used for sommelier build by Google - trying to find a solution for this as well. Please share any findings you have related to these issues.

On a fresh container install in ChromeOS 74, I can't get garcon - and thus most of the integrations with ChromeOS - working. (X11 / sommelier is still working, should note)

Mar 04 08:09:13 penguin systemd[39]: Started Chromium OS Garcon Bridge. Mar 04 08:09:13 penguin garcon[131]: [131]: Server listening on vsock port 10000 Mar 04 08:09:13 penguin garcon[131]: [131]: Failed to notify host system that container is ready: Cannot find VM for ContainerListener Mar 04 08:09:13 penguin garcon[131]: [131]: Failed to set up host notifier

Garcon cant seem to signal to the host that it's there - so stuff like the Terminal app, Files app (?? may be an intersection between cros-sftp and cros-garcon here), etc don't work. The only way into the container is vmc start termina, followed by lxc start penguin / lxc console penguin.

Thanks for packaging this stuff for Arch!