URL for the tar.zst seems wrong in PKGBUILD. This link works: https://github.com/ungoogled-software/ungoogled-chromium-archlinux/releases/download/145.0.7632.109-1/ungoogled-chromium-145.0.7632.109-2-x86_64.pkg.tar.zst
Search Criteria
Package Details: ungoogled-chromium-bin 145.0.7632.116-1
Package Actions
| 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: | 140 |
| Popularity: | 1.99 |
| First Submitted: | 2022-08-27 13:16 (UTC) |
| Last Updated: | 2026-02-26 02:51 (UTC) |
Dependencies (35)
- alsa-lib
- brotli (brotli-gitAUR)
- dbus (dbus-gitAUR, dbus-selinuxAUR, dbus-nosystemd-gitAUR)
- desktop-file-utils (desktop-file-utils-gitAUR)
- flac (flac-gitAUR)
- fontconfig (fontconfig-gitAUR, fontconfig-ubuntuAUR)
- freetype2 (freetype2-qdoled-aw3225qfAUR, freetype2-macosAUR, freetype2-qdoledAUR, freetype2-qdoled-gen3AUR, freetype2-woledAUR, freetype2-gitAUR)
- gtk3 (gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR, gtk3-no_deadkeys_underlineAUR)
- harfbuzz (harfbuzz-gitAUR)
- hicolor-icon-theme (hicolor-icon-theme-gitAUR)
- icu (icu-gitAUR)
- libcups (libcups-gitAUR, cups-gitAUR, libcups-gssapiAUR)
- libffi (libffi-gitAUR)
- libgcrypt
- libjpeg-turbo (mozjpeg-gitAUR, mozjpegAUR, libjpeg-turbo-gitAUR)
- libpng (libpng-gitAUR, libpng-apngAUR)
- libpulse (pulseaudio-dummyAUR, libpulse-gitAUR)
- libva (libva-gitAUR, intel-media-stack-legacy-binAUR, intel-media-stack-binAUR, libva-headlessAUR)
- libwebp (libwebp-gitAUR)
- libxml2 (libxml2-gitAUR, libxml2-meson-gitAUR)
- Show 15 more dependencies...
Required by (161)
- accomplish-ai-bin (requires chromium) (optional)
- aider-chat (requires chromium) (check)
- aider-chat (requires chromium) (optional)
- anylogic-ple (requires chromium) (optional)
- anylogic-ple-8.2.4 (requires chromium) (optional)
- anylogic-professional (requires chromium) (optional)
- anylogic-professional-8.2.4 (requires chromium) (optional)
- anylogic-university (requires chromium) (optional)
- anylogic-university-8.2.4 (requires chromium) (optional)
- aptana-studio (requires chromium) (optional)
- aquatone (requires chromium)
- aquatone-bin (requires chromium)
- aquatone-git (requires chromium)
- arch-wiki-search (requires chromium) (optional)
- archivebox (requires chromium)
- assbreak (requires chromedriver) (make)
- asset-ripper (requires chromium) (optional)
- audible-activator-git (requires chromedriver)
- augenkrebs-git (requires chromium)
- bbb-recorder-git (requires chromium)
- Show 141 more...
Sources (1)
dan361 commented on 2026-02-21 10:23 (UTC)
gothmog123 commented on 2026-02-21 06:10 (UTC)
curl: (22) The requested URL returned error: 404 ==> ERROR: Failure while downloading https://github.com/ungoogled-software/ungoogled-chromium-archlinux/releases/download/145.0.7632.109-2/ungoogled-chromium-145.0.7632.109-2-x86_64.pkg.tar.zst
Mugzx commented on 2026-02-21 05:02 (UTC)
The PKGBUILD for ungoogled-chromium-bin version 145.0.7632.109-2 seems to be filled out incorrectly? The tag on the GitHub link is actually 145.0.7632.109-1.
antdou commented on 2026-02-19 08:28 (UTC) (edited on 2026-02-19 08:30 (UTC) by antdou)
Hi! Had an issue similar to what Barmanji had on 2025-08-24, except now Chromium 145.0.7632.75-2 (latest in AUR) requires GLIBC v. 2.43+; the latest one in the Manjaro repo is 2.42, though. Had to roll back to 144.0.7559.132-2 that I had cached.
Maybe glibc should be explicitly added as a dependency? (I have read the top pinned comment but I unfortunately do not understand, sorry, am a noob)
nich23 commented on 2026-01-12 20:41 (UTC)
Is it support the aarch64 architecture?
gothmog123 commented on 2025-10-30 12:17 (UTC)
Is it possible to install and use this alongside normal chromium? I need both
Barmanji commented on 2025-08-24 04:37 (UTC)
/usr/lib/chromium/chromium: /usr/lib/libc.so.6: version `GLIBC_2.42' not found (required by /usr/lib/chromium/chromium)
For me: I just searched GLIBC in arch repo and installed it. CMD: yay -S glibc 2.42+r17+gd7274d718e6f-1 And GGs
networkException commented on 2025-08-18 01:21 (UTC)
There isn't a release for extra/chromium yet and I currently don't have the capacity to make sure the non ungoogled bits work correctly. Feel free to open a pull request if you can test it or poke https://gitlab.archlinux.org/archlinux/packaging/packages/chromium/
Maoyue commented on 2025-08-17 16:19 (UTC)
https://github.com/ungoogled-software/ungoogled-chromium/issues/3428 Chromium 139.0.7258.127 on Linux merged, but this package didn't get a update yet?
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
chromiumpackage 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