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 8 9 Next › Last »

auditor_3d commented on 2023-06-29 02:04 (UTC) (edited on 2023-06-29 02:22 (UTC) by auditor_3d)

latest update killed my U-C app. here is the error:

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

It appears this may be due to an out of sync upgrade of the icu package? howveer I can't downgrade it to the previous version because it will break other programs that need it as a dependency. Not sure how to fix this.

https://github.com/ungoogled-software/ungoogled-chromium/issues/2401

May be a waiting game for UC to catch up. seems this has happened before, if you see this, wait it out for a while.

networkException commented on 2023-06-15 11:54 (UTC)

@jronald I guess the slighly larger size comes from more metadata, feel free to run diffoscope on the archives though

jronald commented on 2023-06-12 06:13 (UTC) (edited on 2023-06-12 06:14 (UTC) by jronald)

ungoogled-chromium-bin-114.0.5735.106-1-x86_64.pkg.tar.zst is generated from ungoogled-chromium-114.0.5735.106-1-x86_64.pkg.tar.zst, why the size of the former is larger?

$ ls -l *.zst
-rw-r--r-- 1 user user 118089244 Jun 12 14:06 ungoogled-chromium-114.0.5735.106-1-x86_64.pkg.tar.zst
-rw-r--r-- 1 user user 118109352 Jun 12 14:07 ungoogled-chromium-bin-114.0.5735.106-1-x86_64.pkg.tar.zst

networkException commented on 2023-05-31 11:38 (UTC)

@floppyman Make sure your system is up to date. If you are running Manjaro then I sadly cannot guarantee that it will work, you might have to build it yourself

missingSleepDeps commented on 2023-05-12 21:06 (UTC) 

/usr/lib/chromium/chromium: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.31' not found (required by /usr/lib/chromium/chromium)

dreieck commented on 2023-04-27 12:29 (UTC)

Can you please add =${pkgver} to the chromium entry in the provides array?

There is at least one package that has (defined by upstream source) a versioned dependency in chromium.

Regards!

dreieck commented on 2023-04-27 12:27 (UTC)

Can you please add provides=("chromedriver=${pkgver}"), conflicts=('chromedriver')?

Regards!

networkException commented on 2023-04-02 23:45 (UTC)

Yes, I didn't consider all places a version number would need to be bumped unfortunately.

I sincerely hope this fixes the issue for good

PolarianDev commented on 2023-04-02 18:04 (UTC)

It seems networkException forgot to bump the pkgrel of the github build, which then caused it to build the package with the wrong pkgrel.

The remote has tagged the released as -3 but the filename is -1, which is causing a conflict within the PKGBUILD.

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