Package Details: ungoogled-chromium-bin 136.0.7103.59-1

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: 115
Popularity: 10.68
First Submitted: 2022-08-27 13:16 (UTC)
Last Updated: 2025-05-04 21:11 (UTC)

Required by (133)

Sources (1)

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 chromium package 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

Latest Comments

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

aero26 commented on 2023-10-07 15:03 (UTC)

When trying to launch Chromium I get the following error

/usr/lib/chromium/chromium: error while loading shared libraries: libdav1d.so.6: cannot open shared object file: No such file or directory

PolarianDev commented on 2023-10-07 10:53 (UTC)

Its most likely due to the fact the current version was linked against the old dav1d version.

This is why it is recommended to use source packages, in which the package is built against the Arch Linux system libraries, instead of upstream building (and linking) against other versions of libraries provided by distributions such as Ubuntu or Debian (which is common for github actions) which often do not use the latest versions.

Try installing ungoogled-chromium instead, although this takes 5-6 hours to build on modern hardware...

auditor_3d commented on 2023-10-07 03:24 (UTC)

This app breaks every month or so because of the same libraries. I wish someone could figure out why....broken yet again

/usr/lib/chromium/chromium: error while loading shared libraries: libdav1d.so.6: cannot open shared object file: No such file or directory

PolarianDev commented on 2023-10-06 16:03 (UTC)

@eduardoeae AUR doesn't rebuild

eduardoeae commented on 2023-10-06 15:53 (UTC) 

/usr/lib/chromium/chromium: error while loading shared libraries: libdav1d.so.6: cannot open shared object file: No such file or directory

Rebuild required due to the update of dav1d 1.3.0-1

leo_sk commented on 2023-08-21 06:54 (UTC) (edited on 2023-08-21 06:54 (UTC) by leo_sk)

Getting error:

/usr/lib/chromium/chromium: error while loading shared libraries: libre2.so.11: cannot open shared object file: No such file or directory

jronald commented on 2023-08-16 11:31 (UTC) (edited on 2023-08-16 11:31 (UTC) by jronald)

@pixeled /etc/pacman.d/mirrorlist as below works, and it keeps integrity.

SigLevel = PackageRequired
Server=https://archive.archlinux.org/repos/2023/08/15/$repo/os/$arch

pixeled commented on 2023-08-16 06:02 (UTC)

Hi, if you cannot currently start ungoogled-chromium due to a re2 update, one possible temporary fix is to downgrade re2. Download the previous version from the archive (currently, this is the previous version), then simply install it with pacman -U <re2 package file>.

jronald commented on 2023-08-16 03:31 (UTC) (edited on 2023-08-16 04:29 (UTC) by jronald)

failed to start because of re2 upgrade

networkException commented on 2023-08-07 16:23 (UTC)

@gschwarz See https://github.com/ungoogled-software/ungoogled-chromium-archlinux/issues/232

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