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 .. 4 5 6 7 8 9 10 11 12 13 Next › Last »

gschwarz commented on 2023-08-05 16:30 (UTC)

the release rolled out yesterday complains that it cannot find GLIBC_2.38 and thus refuses to launch.

gschwarz commented on 2023-08-04 19:37 (UTC)

The following issue is still present in ungoogled-chromium-bin on Arch: https://github.com/ungoogled-software/ungoogled-chromium/issues/1106

auditor_3d commented on 2023-07-07 18:15 (UTC)

this appears to be resolved.

pavard commented on 2023-06-30 22:45 (UTC) (edited on 2023-06-30 22:48 (UTC) by pavard)

For temporary fix icu-problem, downgrade your packages by archive mirror:

  1. comment all mirros in /etc/pacman.d/mirrorlist
  2. add only one with following strings:
 SigLevel = PackageRequired
 Server=https://archive.archlinux.org/repos/2023/06/28/$repo/os/$arch
  1. execute pacman -Suuyy
  2. done. everything works.
  3. wait for this package updated.

xAsh commented on 2023-06-29 02:05 (UTC)

Indeed, icu was very recently updated to v73, and ungoogled-chromium requires libicui18n.so.72 (which is not provided by any package anymore).

auditor_3d commented on 2023-06-29 02:04 (UTC) (edited on 2023-06-29 02:22 (UTC) by auditor_3d)

latest update killed my U-C app. here is the error:

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

It appears this may be due to an out of sync upgrade of the icu package? howveer I can't downgrade it to the previous version because it will break other programs that need it as a dependency. Not sure how to fix this.

https://github.com/ungoogled-software/ungoogled-chromium/issues/2401

May be a waiting game for UC to catch up. seems this has happened before, if you see this, wait it out for a while.

networkException commented on 2023-06-15 11:54 (UTC)

@jronald I guess the slighly larger size comes from more metadata, feel free to run diffoscope on the archives though

jronald commented on 2023-06-12 06:13 (UTC) (edited on 2023-06-12 06:14 (UTC) by jronald)

ungoogled-chromium-bin-114.0.5735.106-1-x86_64.pkg.tar.zst is generated from ungoogled-chromium-114.0.5735.106-1-x86_64.pkg.tar.zst, why the size of the former is larger?

$ ls -l *.zst
-rw-r--r-- 1 user user 118089244 Jun 12 14:06 ungoogled-chromium-114.0.5735.106-1-x86_64.pkg.tar.zst
-rw-r--r-- 1 user user 118109352 Jun 12 14:07 ungoogled-chromium-bin-114.0.5735.106-1-x86_64.pkg.tar.zst

networkException commented on 2023-05-31 11:38 (UTC)

@floppyman Make sure your system is up to date. If you are running Manjaro then I sadly cannot guarantee that it will work, you might have to build it yourself

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