Getting error:
/usr/lib/chromium/chromium: error while loading shared libraries: libre2.so.11: cannot open shared object file: No such file or directory
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: | 89 |
Popularity: | 3.71 |
First Submitted: | 2022-08-27 13:16 (UTC) |
Last Updated: | 2024-11-15 20:27 (UTC) |
Getting error:
/usr/lib/chromium/chromium: error while loading shared libraries: libre2.so.11: cannot open shared object file: No such file or directory
@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
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>
.
failed to start because of re2 upgrade
the release rolled out yesterday complains that it cannot find GLIBC_2.38 and thus refuses to launch.
The following issue is still present in ungoogled-chromium-bin on Arch: https://github.com/ungoogled-software/ungoogled-chromium/issues/1106
this appears to be resolved.
For temporary fix icu-problem, downgrade your packages by archive mirror:
/etc/pacman.d/mirrorlist
SigLevel = PackageRequired
Server=https://archive.archlinux.org/repos/2023/06/28/$repo/os/$arch
pacman -Suuyy
Indeed, icu was very recently updated to v73, and ungoogled-chromium requires libicui18n.so.72 (which is not provided by any package anymore).
Pinned Comments
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