Package Details: ungoogled-chromium-bin 131.0.6778.264-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: 92
Popularity: 4.45
First Submitted: 2022-08-27 13:16 (UTC)
Last Updated: 2025-01-10 16:45 (UTC)

Required by (129)

Sources (1)

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

Latest Comments

1 2 3 4 5 6 .. 10 Next › Last »

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.

omnigenous commented on 2024-12-08 22:59 (UTC)

@wastelander is systemd dependency is new addition? I'm on artix and using ungoogled-chromium-bin 131.0.6778.108 with no issue.

wastelander commented on 2024-11-07 22:48 (UTC)

It would be nice if the systemd dependency was removed to get the package installed on systemd-less Arch-based distros.

STG commented on 2024-08-18 20:57 (UTC) (edited on 2024-08-18 22:16 (UTC) by STG)

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

MartinVonReich commented on 2024-05-30 17:29 (UTC)

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 . . .

kgw commented on 2024-05-26 22:26 (UTC)

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! ;~)

tomacrisan commented on 2024-05-20 22:52 (UTC)

In other words, the PKGBUILD file, line 28, should be: source=(https://github.com/ungoogled-software/ungoogled-chromium-archlinux/releases/download/$pkgver/ungoogled-chromium-$pkgver-$pkgrel-x86_64.pkg.tar.zst)

DarioTD commented on 2024-05-20 20:14 (UTC)

@pavard the maintainer forgot to append the pkgrel "-1" in 125.0.6422.60 tag This is the correct url

pavard commented on 2024-05-20 19:18 (UTC) 

curl: (22) The requested URL returned error: 404
==> ОШИБКА: Ошибка при загрузке 'https://github.com/ungoogled-software/ungoogled-chromium-archlinux/releases/download/125.0.6422.60-1/ungoogled-chromium-125.0.6422.60-1-x86_64.pkg.tar.zst'
    Прерывание...

1 2 3 4 5 6 .. 10 Next › Last »