Package Details: cros-container-guest-tools-git r275.19eab9e-3

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: duhdugg
Last Packager: duhdugg
Votes: 12
Popularity: 1.14
First Submitted: 2018-05-23 06:53
Last Updated: 2020-09-11 20:21

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

jmogens commented on 2019-12-27 05:00

Anyone else see the systemd-networkd-wait-online.service failing, and the container integrations break after upgrading to systemd 244.1?

jdl commented on 2019-12-11 05:20

Thank you for maintaining this package! Everything works fine on my PixelBook GO.

ava1ar commented on 2019-11-03 03:58

Package updated. Changes:

  • Updating systemd-resolved configuration to avoid DNS names resolution delays on container restart
  • Disabling/masking all not working / not required systemd services after package installation

thagabe commented on 2019-10-29 23:57

@ava1ar Thanks for the info! Looks like the latest crostini got the integrations back!

ava1ar commented on 2019-10-26 22:29

@thagabe This is known issue and nothing to do with Arch:

thagabe commented on 2019-10-26 22:09

Issue: Garcon does not connect to "Files" on ChromeOS

Currently on:

- ChromeOS BETA 78.0.3904.70 Pixelbook i5

- Arch container for ChromeOS x86

- Kernel 4.19.69-06666-g6c4f8cbba24e

- systemd 243.78-1

- journalctl -p 3 -xb:

        Oct 26 14:52:49 penguin garcon[122]: [122]: MIME types file does not

                         exist at: /home/<my home user>/.mime.types

        Oct 26 14:52:55 penguin garcon[122]: [122]: MIME types file does not

                         exist at: /home/<my home user>/.mime.types

        Oct 26 14:54:51 penguin garcon[122]: [122]: MIME types file does not

                         exist at: /home/<my home user>/.mime.types

        Oct 26 14:57:47 penguin garcon[122]: [122]: Failed reading in config

                         file: /home/<my home user>/.config/cros-garcon.conf

        Oct 26 14:57:48 penguin garcon[122]: [122]: Failure with

                         RefreshCache of: Failed to obtain authentication.

        Oct 26 14:57:48 penguin garcon[122]: [122]: Failure performing

                         refresh of package cache, code: 2

        Oct 26 15:01:13 penguin garcon[122]: [122]: MIME types file does not 
                         exist at: /home/<my home user>/.mime.types

ava1ar commented on 2019-10-18 22:34

@sovanyio No issue with xkeyboard-config for me. Up-to-date arch in the container (testing is on) and Chrome OS 78.0.3904.50 (Beta channel).

ava1ar commented on 2019-10-18 22:26

@sovanyio If you use sommelier without the full path, you need to add it to the PATH - this is what you need to do you your side and not related to this package itself.

About Eclipse - I was able to google multiple guides about how to configure HiDPI support for it. I personally don't use it, but was able to configure both Netbeans and IntelliJ IDEA to proper render without sommalier "workaround".

Issue with xkeyboard-config looks familiar, but it was addressed long ago. May be this is something new, I will double check. Are your Arch up-to-date? Which ChromeOS channel / version are you running on Pixelbook?

sovanyio commented on 2019-10-18 22:06

Yeah, so I'm on a pixelbook and I run usually at 80% scaling in ChromeOS. When using the debian container, I typically modify desktop files under /usr/share/applications/ with sommelier -X --scale=.8 --dpi=160 %command and this works very well across apps I use (sublime text, atom, eclipse, intellij).

OOTB adding the sommelier command results in:

$ xdg-open atom.desktop
/usr/sbin/env: 'sommelier': No such file or directory

and the associated desktop file being passed to Chrome is ChOS (which "opens" as a tab).

I ended up appending the cros-tools bin directory to /etc/profile and that appears to be working as expected, though I get another error with that addition, added below.

$ xdg-open atom.desktop 
_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Unsupported high keycode 382 for name <I382> ignored
>                   X11 cannot support keycodes above 255.
>                   This warning only shows for the first high keycode.
> Internal error:   Could not resolve keysym XF86MonBrightnessCycle
> Internal error:   Could not resolve keysym XF86RotationLockToggle
Errors from xkbcomp are not fatal to the X server
[$USER@penguin applications]$ 
(electron4:565): Gtk-WARNING **: 18:00:07.964: cannot open display: :2

Is this now additional incompatible keys in xkeyboard-config? Perhaps expected but should note anyway that launching through ChromeOS GUI fails for both of these situations.

Without setting scaling explicitly through sommelier, the default settings screw up the dpi and scaling on eclipse making it completely unusable (though text is sharp) UI elements are way larger than expected and its generally not a fun time.

ava1ar commented on 2019-10-18 21:15

@sovanyio can you provide more information? First of all, there is 2x scaling using sommelier available out-of-the-box using right click menu in the task bar (this is achieved using separate sommelier instance with 2x scaling). Also, sommelier scaling is not the best from the point of view of visual quality - proper HiDPI support configuration like gives much better result.