| Git Clone URL: | https://aur.archlinux.org/ungoogled-chromium-bin.git (read-only, click to copy) |
|---|---|
| Package Base: | ungoogled-chromium-bin |
| Description: | A lightweight approach to removing Google web service dependency |
| Upstream URL: | https://github.com/ungoogled-software/ungoogled-chromium |
| Keywords: | blink browser privacy web |
| Licenses: | BSD |
| Conflicts: | chromedriver, chromium |
| Provides: | chromedriver, chromium |
| Submitter: | networkException |
| Maintainer: | networkException |
| Last Packager: | networkException |
| Votes: | 152 |
| Popularity: | 5.57 |
| First Submitted: | 2022-08-27 13:16 (UTC) |
| Last Updated: | 2026-07-18 22:34 (UTC) |
While building 148.0.7778.215-1, I get
-> Compressing man and info pages...
libfakeroot internal error: payload not recognized!
==> Checking for packaging issues...
Yet the build seem to be successful. A short run of the installed package also seems to succeed. Hopefully, the issue is similar to comment by Christian Hesse at Aug 24, 2024.
openh264 is now required, but isn't declared as a dependency in the PKGBUILD.
If the packaged /usr/lib/chromium/chromium binary ends up being empty and thus chromium being unusable, you'll need to add the following options to the PKGBUILD:
options=('!strip' '!debug')
and then rebuild the package after that.
Version 147.0.7727.55-1 seems to have a hidden wayland dependency & isn't starting on my (wayland-free) system. It gives the following error:
[488107:488107:0414/145440.863108:ERROR:ui/ozone/platform/wayland/host/wayland_connection.cc:202] Failed to connect to Wayland display: No such file or directory (2)
[488107:488107:0414/145440.863138:ERROR:ui/ozone/platform/wayland/ozone_platform_wayland.cc:281] Failed to initialize Wayland platform
[488107:488107:0414/145440.863148:ERROR:ui/aura/env.cc:246] The platform failed to initialize. Exiting.
Little suggestion: change upstream URL to https://github.com/ungoogled-software/ungoogled-chromium-archlinux so people see the latest release for Arch, not the main repo.
Because there were 3 releases in short succession I was busy with in ungoogled-chromium upstream and CI is still building the latest one. Please see the pinned comment
Why hasn't this package been updated to 146.x?
URL for the tar.zst seems wrong in PKGBUILD. This link works: https://github.com/ungoogled-software/ungoogled-chromium-archlinux/releases/download/145.0.7632.109-1/ungoogled-chromium-145.0.7632.109-2-x86_64.pkg.tar.zst
Pinned Comments
networkException commented on 2025-05-02 13:41 (UTC)
Hello everyone, there's always a lot of confusion when ungoogled-chromium doesn't start because of a system dependency it can't find.
This issue is inherent to Arch Linux package management, there's no mechanism that tracks required rebuilds. Maintainers are expected to push manual pkgrel bumps once a rebuild is required. The
chromiumpackage can somewhat easily handle this, they can also update the package in testing first.People's comments here or on GitHub are how I notice that a rebuild is required, I try to push an update quickly then. Sadly a full rebuild currently takes over 24 hours on GitHub Actions and I'm not exactly maintaining open source software as my dayjob either, so this can take a while.
There's no solution for this really, other than adopting the package into the official repository maybe (I cannot do that). Note that for Manjaro users even a rebuild might not be enough as there can always be mismatches in what system library versions are available.
networkException commented on 2022-09-20 17:36 (UTC)
Please note that normally it's not required to flag this package as out of date. I usually tag releases in the main ungoogled-chromium repository and update the arch packaging right afterwards.
If the package hasn't updated after an ungoogled-chromium release GitHub Actions might still be building or the ungoogled-chromium patchset got updated for non Linux platforms only to match their upstream release cycle