Package Details: cros-container-guest-tools-git r403.0c2dcc71-1

Git Clone URL: (read-only, click to copy)
Package Base: cros-container-guest-tools-git
Description: Linux guest tools for the Crostini containers on ChromeOS
Upstream URL:
Keywords: chromeos containers crostini lxc
Licenses: custom
Submitter: ava1ar
Maintainer: mshaugh
Last Packager: mshaugh
Votes: 19
Popularity: 0.000853
First Submitted: 2018-05-23 06:53 (UTC)
Last Updated: 2023-04-25 16:51 (UTC)

Latest Comments

1 2 3 4 5 6 .. 11 Next › Last »

rahil627 commented on 2023-08-16 23:51 (UTC) (edited on 2023-08-17 02:28 (UTC) by rahil627)

i get a bunch of permission errors, running it as a user (which i think i'm supposed to do..?)

:: Running post-transaction hooks...\ (1/5) Reloading system manager configuration...\ (2/5) Reloading device manager configuration...\ LNXSYSTM:00: Failed to write 'change' to '/sys/devices/LNXSYSTM:00/uevent': Permission denied (... a ton of similar errors for usb, cmos, memory, virtual, etc.)

maybe related to this warning about my sudoers permissions?:\ warning: directory permissions differ on /etc/sudoers.d/\ filesystem: 750 package: 755\ warning: directory permissions differ on /usr/share/polkit-1/rules.d/\ filesystem: 750 package: 755

but i read that sudoers is supposed to have 0440 permissions...

mount | grep vda /dev/vda on /opt/google/cros-containers type ext4 (ro,relatime) maybe should the file-system should be writeable?

mio-19 commented on 2023-06-27 13:28 (UTC)

The terminal would auto close before arch is fully booted

mio-19 commented on 2023-06-04 15:18 (UTC)

From 108 there is another cros guest tools called cros-im. What about packaging it for arch?

nallekarhu commented on 2023-04-19 20:11 (UTC) (edited on 2023-04-19 20:12 (UTC) by nallekarhu)

@mshaugh please update cros-garcon-conditions.conf as described by @agrueneberg

abhinav commented on 2023-04-18 12:20 (UTC)

After upgrading to ChromeOS 112, the Terminal would time out trying to connect to the container. Just confirming that the fix suggested by @agrueneberg resolved the problem.

agrueneberg commented on 2023-03-14 21:42 (UTC)

/dev/.host_ip has recently been removed:

Therefore, ConditionPathExists=/dev/.host_ip needs to be removed from cros-garcon-conditions.conf for cros-garcon to start (I'm currently on Beta 112), otherwise:

Mar 14 22:28:20 arch systemd[91]: Chromium OS Garcon Bridge was skipped because of an unmet condition check (ConditionPathExists=/dev/.host_ip).

mx.bug commented on 2023-02-25 21:16 (UTC)

This PKGBUILD is broken.

==> Making package: cros-container-guest-tools-git r393.3972ce85-1 (Sat Feb 25 20:58:00 2023)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Starting pkgver()...
==> Removing existing $pkgdir/ directory...
==> Entering fakeroot environment...
==> Starting package()...
install: cannot stat '/home/bug/.cache/paru/clone/cros-container-guest-tools-git/src/cros-container-guest-tools/cros-sftp/cros-sftp.service': No such file or directory

The service file indeed does not exist, because cros-sftp has been deprecated and is no longer needed, because sftp is launched by a different means now.

agrueneberg commented on 2023-02-04 19:29 (UTC) (edited on 2023-02-05 09:15 (UTC) by agrueneberg)

Is "Linux files" integration working for anyone out of the box? If I click on the entry in the Files app, no files are shown. The cros-garcon user service in Arch responds as follows:

Feb 04 20:25:14 arch garcon[219]: [219]: sftp: accepted connection from vsock:2:3612554745
Feb 04 20:25:14 arch garcon[219]: [219]: Failed to execute requested program in child process: No such file or directory
Feb 04 20:25:14 arch garcon[219]: [219]: sftp: failed to spawn child process: No child processes (10)
Feb 04 20:25:14 arch garcon[219]: [219]: sftp: accept waiting

garcon is trying to execute /usr/lib/openssh/sftp-server (see, which in Arch is in /usr/lib/ssh. Symlinking fixes the issue:

sudo mkdir /usr/lib/openssh
sudo ln -s /usr/lib/ssh/sftp-server /usr/lib/openssh/

What's a good way to deal with this as part of this package given that we cannot fix the path directly?

felipecrp commented on 2023-02-03 02:24 (UTC)

@allexj you must use systemctl --user

systemctl --user enable sommelier@0
systemctl --user enable sommelier@1
systemctl --user enable sommelier-x@0
systemctl --user enable sommelier-x@1
systemctl --user start sommelier@0
systemctl --user start sommelier@1
systemctl --user start sommelier-x@0
systemctl --user start sommelier-x@1

allexj commented on 2022-11-22 23:44 (UTC)

If I try to enable sommelier@0.service, sommelier-x@0.service, sommelier@1.service and sommelier-x@1.service all of them are units not found.