Ungoogled Chromium for Void Linux

Ungoogled Chromium template and builds for Void Linux, based on the void-packages chromium template.

Content Overview

• Building from sources
• Binary release
  • Available builds
  • Installing the binary package
• Troubleshooting
  • Musl crashes mitigation
  • General tweaks
• Credits

Building from source

Note

Consult void-packages documentation for more information about setting it up.

Quick start

Building packages natively for the musl C library

The lazy way:

git clone --depth=1 https://github.com/xJayMorex/ungoogled-chromium-void.git
cd ungoogled-chromium-void
./build.sh

Binary release

./xbps-src show-options ungoogled-chromium
=> ungoogled-chromium-142.0.7444.59_1: the following build options are set:
   clang: Use clang to build (ON)
   libcxx: Use bundled libc++ (ON)
   pipewire: Enable support for screen sharing for WebRTC via PipeWire (ON)
   pulseaudio: Enable support for the PulseAudio sound server (ON)
   qt6: Enable support for qt6 (ON)
   vaapi: Enable support for VA-API (ON)
   debug: Build with debug symbols (OFF)
   drumbrake: WebAssembly Interpreter (OFF)
   lto: Enable Link Time Optimization (OFF)
   sndio: Enable support for the sndio sound server (OFF)

Available builds

Available builds:

• x86_64
• x86_64-musl
• aarch64

Installing the binary package

Method 1 - manual update

Download the xbps package from the releases page, index and install the package:

xbps-rindex -a *.xbps
sudo xbps-install -vR $PWD ungoogled-chromium

Method 2 - updates handled by xbps-install

Add the releases page as a repository:

cat << EOF > /etc/xbps.d/20-ungoogled-chromium.conf
repository=https://github.com/xJayMorex/ungoogled-chromium-void/releases/latest/download
EOF
xbps-install -Su ungoogled-chromium

First xbps-install -S run it will ask to import the repository key, same as 8e:9c:f9:9a:cd:77:2a:3c:25:54:61:c1:36:25:f0:4f.plist.

Troubleshooting

• Although it is not included in the run dependencies, gtk+3 package must be installed.
• To enable VAAPI add --enable-features=VaapiVideoDecoder to CHROME_FLAGS environment variable.
  More info vaapi.md. Also check Void Handbook in case of problems.
• For VAAPI --disable-features=UseChromeOSDirectVideoDecoder might also be needed.
  Check in chrome://gpu if Video Decode: Hardware accelerated.

Musl crashes mitigation

• Make sure you have dbus running (on glibc it doesn't matter).
  Symptoms: crashes, pages stalling and refusing to load until browser restart, plugin crashes.
• Try adding --js-flags=--jitless to CHROME_FLAGS. If nothing else, it's a security hardening option.

General tweaks

• Lower ram usage: --renderer-process-limit=2 renderer-process-limit.
• Reduce disk activity: --disk-cache-size=1 --v8-cache-options=none disk-cache-size, v8-cache-options.
• Dark Mode: chrome://flags/#enable-force-dark.
• Global media controls can cause crashes either by opening or closing it, as described in this issue.
  Either avoid using the feature or disable it completely (--disable-features=GlobalMediaControls).

Credits

• Ungoogled Chromium
• Ungoogled Chromium Void upstream
• The Void source packages collection
• The Void (Linux) distribution