Package Details: ungoogled-chromium-bin 137.0.7151.68-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: 123
Popularity: 10.66
First Submitted: 2022-08-27 13:16 (UTC)
Last Updated: 2025-06-04 17:47 (UTC)

Required by (136)

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 2 3 4 5 6 7 8 9 .. 13 Next › Last »

rubin55 commented on 2025-02-21 20:15 (UTC)

... So flac just upgraded..

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

Mackin_cheese commented on 2025-02-20 22:09 (UTC)

@marek22k

This is a known error due to a core package update. They are currently working on a new build and will update.

marek22k commented on 2025-02-20 22:02 (UTC)

Hi, I cannot open Chromium:

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

Mackin_cheese commented on 2025-02-20 16:35 (UTC)

@countercraft that's on me, didn't realize that the AUR maintainer is part of the ungoogled-chromium team

countercraft commented on 2025-02-20 16:32 (UTC)

@Mackin_cheese Upstream is this case is the Ungoogled team themselves, they build the Arch Linux binary that this package uses.

It will be updated when this build finishes: https://github.com/ungoogled-software/ungoogled-chromium-archlinux/actions/runs/13435254841

It seems that @networkException also removed icu from the chromium system libs, so that should do what @Kyuunex asked.

Mackin_cheese commented on 2025-02-20 16:07 (UTC)

@Kyuunex this package is is a bin package, meaning there's no compiling from source, it's the bin provided directly by upstream.

Kyuunex commented on 2025-02-20 11:49 (UTC)

Rebuild required. Consider building this in a way it does not stop working when icu updates. Like how Google builds Chrome.

networkException commented on 2025-01-06 18:35 (UTC)

@rubin55 I can't reproduce this on an up to date Arch. Are you using a derivative? If so that's not supported

rubin55 commented on 2025-01-06 15:09 (UTC) (edited on 2025-01-06 20:17 (UTC) by rubin55)

I'm getting this after upgrading packages this morning:

/usr/lib/chromium/chromium: symbol lookup error: /usr/lib/chromium/chromium: undefined symbol: unzGetCurrentFileZStreamPos64

Update: this was because I had minizip-ng-compat and minizip-ng installed. I didn't have the minizip package. The latest update of the minizip package, 1:1.3.1-2, conflicts with minizip-ng-compat apparently. I'm not sure, but when I installed the regular minizip package, ungoogled-chromium started working again.

I suspect (I can't remember precisely) that minizip-ng-compat "provides" minizip but not a compatible one anymore? Strangeness.

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