Package Details: ungoogled-chromium 131.0.6778.264-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: 353
Popularity: 3.68
First Submitted: 2016-12-19 08:08 (UTC)
Last Updated: 2025-01-09 17:44 (UTC)

Dependencies (49)

Required by (135)

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 .. 25 26 27 28 29 30 31 32 33 34 35 .. 66 Next › Last »

JstKddng commented on 2020-11-18 21:59 (UTC)

@tomcourtier

Check the pinned comment, you have a lot of options for binary downloads there.

zocker_160 commented on 2020-11-18 21:58 (UTC)

@tomcourtier I actually made an ungoogled-chromium-bin package multiple times, but it got removed each time, because the binary package was from an untrusted source, even though I offered the full build log for each package.

<deleted-account> commented on 2020-11-18 21:28 (UTC)

Would it be too much to ask for some very capable and lovely person to create "ungoogled-chromium-bin" for those without mega hardware, and not wanting to add third-party repos? Thanks in advance for your consideration.

followait commented on 2020-11-18 00:43 (UTC)

@bkb Have you enabled swap partition or swap file?

BTW As in my test, a swap file of 2G can make the build successful. Without swap file or swap partition, though set vm.swappiness=10, the build fails.

lahwaacz commented on 2020-11-17 15:36 (UTC)

@bkb That's not quite surprising, since you both have 2 GB per core. There is also probably one file which takes much more memory to compile than others...

bkb commented on 2020-11-17 13:40 (UTC)

Lol, considering that with my tiny 8gb 4 cores I stall at the same step than you, I suggest that it's the Linux build who's laggy, more than our architecture who is weak

followait commented on 2020-11-16 01:14 (UTC) (edited on 2020-11-16 13:09 (UTC) by followait)

@lahwaacz Alright, 16GB memory for 8 cores 16 threads is not enough, thanks very much

lahwaacz commented on 2020-11-15 13:33 (UTC)

@followait It depends more on how many CPU cores you have. If you used only one core for the build, even 4 GB of memory should be enough, maybe less...

followait commented on 2020-11-15 13:30 (UTC)

@lahwaacz You are right. With vm.swappiness=60 by default, 16GB memory is not enough. After enabling swapfile with 4GB and set vm.swappiness=10, it works. Thanks

lahwaacz commented on 2020-11-15 13:01 (UTC)

@bkb It's not a compiler's responsibility to deal with such things. If you want to use HDD instead of RAM, you need to configure swap accordingly. But that will be pretty slow, probably even slower than if you disabled parallelization completely. What I'd recommend instead, is instructing the build system to spawn less compiler processes in parallel and thus reducing the memory requirements. See ninja -h for the available options, the -j flag is probably a good start.

« First ‹ Previous 1 .. 25 26 27 28 29 30 31 32 33 34 35 .. 66 Next › Last »