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

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: mshaugh
Last Packager: mshaugh
Votes: 19
Popularity: 0.004442
First Submitted: 2018-05-23 06:53 (UTC)
Last Updated: 2023-04-25 16:51 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 Next › Last »

ava1ar commented on 2020-04-30 03:21 (UTC)

@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 (UTC) (edited on 2020-04-30 02:06 (UTC) by cadilhac)

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 (UTC)

Updated to latest from upstream.

@mmberlin, link was added.

mmberlin commented on 2020-04-05 02:40 (UTC) (edited on 2020-04-05 02:44 (UTC) by mmberlin)

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 (UTC) (edited on 2019-12-27 05:02 (UTC) by ava1ar)

jmogens,

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

jmogens commented on 2019-12-27 05:00 (UTC)

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 (UTC)

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

ava1ar commented on 2019-11-03 03:58 (UTC) (edited on 2019-11-03 03:58 (UTC) by ava1ar)

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 (UTC)

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

ava1ar commented on 2019-10-26 22:29 (UTC)

@thagabe This is known issue and nothing to do with Arch: https://bugs.chromium.org/p/chromium/issues/detail?id=1000966

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 Next › Last »