Package Details: ungoogled-chromium-bin 136.0.7103.59-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: 115
Popularity: 10.68
First Submitted: 2022-08-27 13:16 (UTC)
Last Updated: 2025-05-04 21:11 (UTC)

Required by (133)

Sources (1)

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 chromium package 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

Latest Comments

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

tomacrisan commented on 2025-05-04 17:06 (UTC)

@networkException I appreciate your work; building ungoogle-chromium takes my laptop over 24 hours with all four core running at 90%-100% so I very much appreciate having a -bin version available.

pross commented on 2025-05-02 14:25 (UTC)

@networkException we appreciate your dedication to this package!

For me the -2 version released yesterday fixed the libxml2 issue, I installed compat package mentioned below anyway just in case anything else breaks that needs it.

Thanks again!

Switch123456789 commented on 2025-05-02 14:21 (UTC)

I got it working again by installing: https://archlinux.org/packages/extra/x86_64/libxml2-legacy/

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

saroumane commented on 2025-05-02 00:30 (UTC)

Workaround for the libxml2 update that breaks compatibility with this binary : you may try to install libxml2-compat from AUR : https://aur.archlinux.org/packages/libxml2-compat

Of course, if you have enough RAM, CPU and time, you can try instead to build from source (switch to ungoogled-chromium package).

RSG245 commented on 2025-05-01 22:55 (UTC)

Thanks for fix bug with libxml2

Mackin_cheese commented on 2025-05-01 17:47 (UTC)

@impulse it is NOT a bug in the PKGBUILD. this is a binary release and as such is built with the deps available at that time. Libxml2.so.2 has been removed by the upstream, there is nothing wrong with the PKGBUILD, you would have to either wait until this gets patched by either Arch developers or ungoogled-chromium developers OR until libxml2 developers release a new version that brings so.2 back into the mix

impulse commented on 2025-05-01 17:41 (UTC)

@networkException ive used this package over a long period of time, i keep having this same issue (just with different libraries), upon system update.

This time it was: /usr/lib/chromium/chromium: error while loading shared libraries: libxml2.so.2: cannot open shared object file: No such file or directory

I consider this a bug in the PKGBUILD.

Ive seen it happen with the other system deps, where a system dependency is updated and the chromium binary is tightly coupled to the specific version it was built with. (often when the minor semver of the dep changes in my experiance).

Does anyone have suggestions for a permanent fix? we could bundle the deps in the binary (not ideal) or dynamically load system libs in such a way that it can handle minor or patch increments (for major changes of course, we should throw this error)

Mackin_cheese commented on 2025-05-01 15:20 (UTC)

@Kyuunex, the libxlm2 error has been affecting several packages, that is not on the developers of ungoogled-chromium, that's on the developers of libxml2 for making a backwards incompatible update and then upgrading the so name. That's never on ungoogled-chromium

Kyuunex commented on 2025-05-01 09:28 (UTC)

@OXDBXKXO Apologies for my previous comment. I am simply frustrated that a long running problem isn't getting as much attention as it deserves, while it's totally solvable. I've been running ungoogled-chromium for years and it's been a constant source of frustration.

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