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

Git Clone URL: https://aur.archlinux.org/cros-container-guest-tools-git.git (read-only, click to copy)
Package Base: cros-container-guest-tools-git
Description: Linux guest tools for the Crostini containers on ChromeOS
Upstream URL: https://chromium.googlesource.com/chromiumos/containers/cros-container-guest-tools
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 »

duhdugg commented on 2020-09-09 22:06

Yes, I'm up for the task.

ava1ar commented on 2020-09-09 21:54

@drelyn86,

Are you interested in picking up the package support? I am not using ChromeOS and Chromebooks anymore. Let me know if you are interested.

duhdugg commented on 2020-09-09 18:17

I just did a fresh install and noticed a couple issues.

  1. xorg-xrdb and xorg-xsetroot need installed to get the default sommelier config working as intended (see /etc/sommelierrc)

  2. cros-notificationd.service needs installed to /usr/lib/systemd/user/ to get notifications working:

install -m644 -D ${srcdir}/${_pkgname}/cros-notificationd/cros-notificationd.service ${pkgdir}/usr/lib/systemd/user/cros-notificationd.service

ava1ar commented on 2020-06-07 05:17

@thagabe

Thanks for the notification, package is fixed. Google used dpkg-divert feature to update system configuration files, owned by other package. Unfortunately, Arch doesn't have such functionality, so I have to come up with other approach.

Manual command execution required after the package update to make PulseAudio work. Tested and verified working.

If someone has better ideas for the issue, please drop me a message. Thanks!

thagabe commented on 2020-06-06 23:35

As of 06//06/2020 I am getting this error with a clean build

install: cannot stat '/home/<home directory>/.cache/yay/cros-container-guest-tools-git/src/cros-container-guest-tools/cros-pulse-config/cros-pulse-config.service': No such file or directory
==> ERROR: A failure occurred in package().
    Aborting...
Error making: cros-container-guest-tools-git

EDIT: here is some info I dug up, looks like the config file is phased out https://chromium.googlesource.com/chromiumos/containers/cros-container-guest-tools/+/0767a9fc6cb36b0349326714bc0c60a69e64ce07

ava1ar commented on 2020-04-30 03:21

@cadilhac, interesting that key codes issues were fatal to the Sommelier earlier (about a year ago) and they these warnings were present but never cause issues. Somehow you got old issue back, however my setup works fine, showing same errors on start.

cadilhac commented on 2020-04-30 00:53

I'm having something similar to @savanyio, where sommelier-x@0 does not start because of xkbcomp.

Apr 30 00:44:56 arch sommelier[27409]: _FontTransOpen: Unable to Parse address  /usr/share/fonts/cyrillic
Apr 30 00:44:56 arch sommelier[27409]: _FontTransOpen: Unable to find transport for
Apr 30 00:44:56 arch sommelier[27409]: _FontTransOpen: Unable to find transport for
Apr 30 00:44:56 arch sommelier[27409]: _FontTransOpen: Unable to Parse address  /usr/share/fonts/Type1
Apr 30 00:44:56 arch sommelier[27409]: _FontTransOpen: Unable to Parse address  /usr/share/fonts/100dpi
Apr 30 00:44:56 arch sommelier[27409]: _FontTransOpen: Unable to Parse address  /usr/share/fonts/75dpi
Apr 30 00:44:56 arch sommelier[27420]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Apr 30 00:44:56 arch sommelier[27420]: > Error:            Illegal keycode 372 for name <I372>
Apr 30 00:44:56 arch sommelier[27420]: >                   Must be in the range 8-255 inclusive
Apr 30 00:44:56 arch sommelier[27420]: > Error:            Illegal keycode 382 for name <I382>
Apr 30 00:44:56 arch sommelier[27420]: >                   Must be in the range 8-255 inclusive
Apr 30 00:44:56 arch sommelier[27420]: > Error:            Illegal keycode 569 for name <I569>
Apr 30 00:44:56 arch sommelier[27420]: >                   Must be in the range 8-255 inclusive
Apr 30 00:44:56 arch sommelier[27420]: > Error:            Illegal keycode 380 for name <I380>
Apr 30 00:44:56 arch sommelier[27420]: >                   Must be in the range 8-255 inclusive
Apr 30 00:44:56 arch sommelier[27420]: Errors from xkbcomp are not fatal to the X server
Apr 30 00:44:56 arch sommelier[27423]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Apr 30 00:44:56 arch sommelier[27423]: > Error:            Illegal keycode 372 for name <I372>
Apr 30 00:44:56 arch sommelier[27423]: >                   Must be in the range 8-255 inclusive
Apr 30 00:44:56 arch sommelier[27423]: > Error:            Illegal keycode 382 for name <I382>
Apr 30 00:44:56 arch sommelier[27423]: >                   Must be in the range 8-255 inclusive
Apr 30 00:44:56 arch sommelier[27423]: > Error:            Illegal keycode 569 for name <I569>
Apr 30 00:44:56 arch sommelier[27423]: >                   Must be in the range 8-255 inclusive
Apr 30 00:44:56 arch sommelier[27423]: > Error:            Illegal keycode 380 for name <I380>
Apr 30 00:44:56 arch sommelier[27423]: >                   Must be in the range 8-255 inclusive
Apr 30 00:44:56 arch sommelier[27423]: Errors from xkbcomp are not fatal to the X server
Apr 30 00:44:56 arch sommelier[27409]: XKB: Failed to compile keymap
Apr 30 00:44:56 arch sommelier[27409]: Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config.
Apr 30 00:44:56 arch sommelier[27409]: (EE)
Apr 30 00:44:56 arch sommelier[27409]: Fatal server error:
Apr 30 00:44:56 arch sommelier[27409]: (EE) Failed to activate virtual core keyboard: 2(EE)

That's on Acer Chromebook Spin 13, following the instructions from the Wiki. Any clue?

EDIT: Removing the offending keycodes in /usr/share/X11/xkb/keycodes/evdev solved the problem.

ava1ar commented on 2020-04-05 18:27

Updated to latest from upstream.

@mmberlin, link was added.

mmberlin commented on 2020-04-05 02:40

Can you add the below link to the PKG build to allow for .desktop file calls to the sommelier service for rescaling?

ln -sf /opt/google/cros-containers/bin/sommelier /usr/bin

Right now you have to call the entire somelier path in each .desktop file. This would be consistent with the standard Debian methods.

ava1ar commented on 2019-12-27 05:01

jmogens,

Yes, this is known issue - check out https://wiki.archlinux.org/index.php/Chrome_OS_devices/Crostini#No_network_in_container