| 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: | 107 |
| Popularity: | 12.76 |
| First Submitted: | 2022-08-27 13:16 (UTC) |
| Last Updated: | 2025-03-10 22:37 (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.
@Kyuunex this package is is a bin package, meaning there's no compiling from source, it's the bin provided directly by upstream.
Rebuild required. Consider building this in a way it does not stop working when icu updates. Like how Google builds Chrome.
@rubin55 I can't reproduce this on an up to date Arch. Are you using a derivative? If so that's not supported
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.
@wastelander is systemd dependency is new addition? I'm on artix and using ungoogled-chromium-bin 131.0.6778.108 with no issue.
It would be nice if the systemd dependency was removed to get the package installed on systemd-less Arch-based distros.
validity check error for 127.0.6533.119-1. Something is going on at github and there is 2 different releases for 127.0.6533.119-1. Install worked after change source to replace "-2" instead of $pkgrel for the download folder:
https://github.com/ungoogled-software/ungoogled-chromium-archlinux/releases/download/$pkgver-2/ungoogled-chromium-$pkgver-$pkgrel-x86_64.pkg.tar.zst
For anybody interested in Google Chrome/Chromium (Stable, Beta, Dev) releases, you can check this website out:
https://chromiumdash.appspot.com/releases?platform=Linux
There is everything . . .
I must admit I am unable to get the latest build to start. I have tried several of the fixes to no avail...I am reduced to using Firefox! ;~)
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