Package Details: ungoogled-chromium 131.0.6778.85-1

Git Clone URL: https://aur.archlinux.org/ungoogled-chromium.git (read-only, click to copy)
Package Base: ungoogled-chromium
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-3-Clause
Conflicts: chromedriver, chromium
Provides: chromedriver, chromium
Submitter: ilikenwf
Maintainer: JstKddng (networkException)
Last Packager: networkException
Votes: 350
Popularity: 3.50
First Submitted: 2016-12-19 08:08 (UTC)
Last Updated: 2024-11-20 21:14 (UTC)

Required by (137)

Sources (14)

Pinned Comments

JstKddng commented on 2022-05-06 14:37 (UTC) (edited on 2022-06-27 13:48 (UTC) by JstKddng)

A new va-api patch for wayland has been added. Required flags for it to work are the following, thanks to @acidunit

--disable-features=UseChromeOSDirectVideoDecoder
--enable-hardware-overlays

JstKddng commented on 2020-07-19 06:34 (UTC)

You can get prebuilt binaries here:

https://github.com/ungoogled-software/ungoogled-chromium-archlinux#binary-downloads

seppia commented on 2018-12-12 21:34 (UTC)

Please do NOT flag this package as out of date in relation to official chromium releases.

This is NOT Google Chromium and new releases come after additional work of the ungoogled-chromium contributors, so they may not be ready, nor available for days or even weeks after a new version of official chromium is released.

Please refer to https://github.com/Eloston/ungoogled-chromium/tags for ungoogled-chromium releases. Use those and please flag this package as out of date only if a newer release is present there. I will update the PKGBUILD as soon as I can every time a new release comes out.

Thanks

Latest Comments

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

randomnobody commented on 2024-03-20 06:19 (UTC)

I'm getting linking errors because my C/C++ objects are targeting x86_64-pc-linux-gnu and rust is targeting x86_64-unknown-linux-gnu. rustc doesn't even seem to support x86_64-pc-linux-gnu as valid target. See example below.

ld.lld: error: Linking two modules of different target triples: 'obj/base/nodebug_assertion/nodebug_assertion.o' is 'x86_64-pc-linux-gnu' whereas 'obj/components/qr_code_generator/libcomponents_sqr_ucode_ugenerator_cqr_ucode_ugenerator_uffi_uglue.rlib(libcomponents_sqr_ucode_ugenerator_cqr_ucode_ugenerator_uffi_uglue.components_sqr_ucode_ugenerator_cqr_ucode_ugenerator_uffi_uglue.93cc98de3648a0e9-cgu.0.rcgu.o at 8722)' is 'x86_64-unknown-linux-gnu'

jahway603 commented on 2024-02-05 13:40 (UTC)

Build fails as it appears REVERT-simplify-blink-NativeValueTraitsBase.patch ... FAILED has changed.

JstKddng commented on 2024-01-28 21:17 (UTC)

Latest version requires internet access due to using experimental rust version. Until then the OBS won't be able to build.

xiota commented on 2023-12-19 00:31 (UTC) (edited on 2023-12-19 00:35 (UTC) by xiota)

Consider adding libicui18n.so and libicuuc.so to depends to make easier to determine need to rebuild for icu updates.

pacman will attempt to detect issues during upgrade and display error similar to: 

:: installing icu (74.2-1) breaks dependency 'libicuuc.so=73-64' required by ungoogled-chromium

<deleted-account> commented on 2023-12-18 13:58 (UTC)

Could you please add https://aur.archlinux.org/packages/chromium-extension-web-store to optdepends?

Kyuunex commented on 2023-11-29 11:55 (UTC)

unable to build either

../../third_party/blink/renderer/core/xml/xsl_style_sheet_libxslt.cc:125:26: error: no matching constructor for initialization of 'XMLDocumentParserScope'

randomnobody commented on 2023-11-23 17:19 (UTC)

I'm getting a compile error regarding a libxml2 function with 119.0.6045.159-1

../../third_party/blink/renderer/core/xml/xslt_processor_libxslt.cc:137:7: error: no matching function for call to 'xmlSetStructuredErrorFunc'

/usr/include/libxml2/libxml/xmlerror.h:897:5: note: candidate function not viable: no known conversion from 'void (void *, xmlError *)' (aka 'void (void *, _xmlError *)') to 'xmlStructuredErrorFunc' (aka 'void (*)(void *, const _xmlError *)') for 2nd argument

7Ji commented on 2023-08-18 13:50 (UTC)

@Kyuunex

when icu or re2 or whatever get updated, ungoogled chromium does not stop launching? In other words, make it so it does not rely on system installation of re2 or icu or anything it needs a specific version of

In that case why not try the flatpak version of ungoogled chromium? A big advantage of building programs that link to your system libraries is to keep both the programs themselves and the libraries up-to-date and safe against latest vulnerabilities. For each library you want to freeze alongside with a binary, you leave a forgotten library that'll bite you in the future with some fresh 0-days. For Google themselves, they could maintain the Chrome release with all libraries up-to-date as if they're maintaining a mini distro (with that many dependencies, it almost is), but here even keeping the ungoogled-chromium AUR package up-to-date alone is already that time-consuming for the only maintainers. The flatpak version on the other hand could at least hold the libraries back in the sandbox, which means no more breaking chromium so you could try it.

(BTW, I'm using prebuilt ungoogled-chromium package from archlinuxcn repo for my x86-64 devices, and build the package by myself for my aarch64 devices.)

Kyuunex commented on 2023-08-16 21:12 (UTC) (edited on 2023-08-16 21:18 (UTC) by Kyuunex)

Any chance you can modify the build script in a way so that when icu or re2 or whatever get updated, ungoogled chromium does not stop launching? In other words, make it so it does not rely on system installation of re2 or icu or anything it needs a specific version of. Just like prebuilt Chrome.

I should mention, "just rebuild" is the wrong answer, as rebuilding takes 4 hours, (even on an 8 core), during which time not only I have downtime browsing, but also using my pc due to 100% cpu usage.

I think some improvements are warranted due to the long build time and the unlikelyness of this moving to [extra] any time soon.

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