Package Details: ungoogled-chromium-bin 131.0.6778.85-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: 89
Popularity: 3.50
First Submitted: 2022-08-27 13:16 (UTC)
Last Updated: 2024-11-21 19:44 (UTC)

Required by (130)

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

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

magnus commented on 2024-05-20 07:48 (UTC)

I followed @Gozenka's suggestion, though I started from libicu53 here on AUR and made the following changes:

diff --git a/PKGBUILD b/PKGBUILD
index 88dd4b9..d3fd08a 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -1,17 +1,17 @@
 # Maintainer: William Tang <galaxyking0419@gmail.com>

-pkgname=libicu53
-pkgver=53.2
+pkgname=libicu74
+pkgver=74.1
 pkgrel=2
 pkgdesc='International Components for Unicode library (version 53)'
 arch=('x86_64')
 url='https://icu.unicode.org'
 license=('custom:icu')
 depends=('gcc-libs')
-provides=(libicu{data,i18n,io,test,tu,uc}.so.53)
+provides=(libicu{data,i18n,io,test,tu,uc}.so.74)

 source=("https://github.com/unicode-org/icu/releases/download/release-${pkgver//./-}/icu4c-${pkgver//./_}-src.tgz")
-sha512sums=('fa3a7c9e388d263d548a02a1e4a63358c24883b4b6d7b29715fb333b96ba193d6c1fef363dafb96097565cf4baf3c1e3be3da5ed1647edf30757a4a65286970b')
+sha256sums=('86ce8e60681972e60e4dcb2490c697463fcec60dd400a5f9bffba26d0b52b8d0')

 build() {
    cd icu/source

Just in case someone else is unable to wait for a fix from the maintainer :D

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

in my memory, this is not the first problem caused by updating the icu version. maybe it's worth linking to it statically?

ramenu commented on 2024-05-19 20:35 (UTC)

@Gozenka It's not just you. I'm getting the same problem.

Gozenka commented on 2024-05-19 20:31 (UTC) (edited on 2024-05-19 20:53 (UTC) by Gozenka)

icu got updated to 75, and current version of ungoogled-chromium-bin fails to launch now, looking for icu 74 libraries. Please let me know if this is not a package issue and if I am missing something.

Edit: I edited the icu73-bin AUR PKGBUILD to point to the 74 release, and it works after installing that. (Just to avoid downgrading.)

knm100 commented on 2024-05-06 14:18 (UTC)

if this rev have been patched text-input-v3 ?

Rikj000 commented on 2024-03-02 09:19 (UTC) (edited on 2024-03-04 18:49 (UTC) by Rikj000)

Since a recent update ungoogle-chromium-bin
started setting itself as the default browser after each update.
(on KDE Plasma v5.27.10)

Can this behavior be disabled?

It quickly gets very annoying to always go to:
Settings => Applications => Default Applications => Toggle Web browser
back to what I had manually configured

Related Github issue with possible solutions:
https://github.com/ungoogled-software/ungoogled-chromium-archlinux/issues/260

xlash123 commented on 2024-01-13 17:29 (UTC)

I was getting a 404 when trying to update this, but after clearing the cache with yay -Scc, it was able to download the correct file and the update completed successfully.

0BAD-C0DE commented on 2024-01-13 10:04 (UTC)

I could install it with paru only after I cleaned up the cache with "rm -fr ~/.cache/paru/clone/ungoogled-chromium-bin" . FWIM.

alyssile commented on 2024-01-13 06:29 (UTC)

Make sure you refresh the PKGBUILD to indicate pkgrel=1 not pkgrel=2, I was getting 404 until I pulled the new PKGBUILD

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