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 .. 21 22 23 24 25 26 27 28 29 30 31 .. 66 Next › Last »

bsdice commented on 2021-03-16 14:26 (UTC) (edited on 2021-03-16 14:29 (UTC) by bsdice)

@JstKddng

maybe your server has bad ram ? The OBS with 16GB of ram and 18 parallel jobs finishes without a problem.

RAM is good, edac-util reports no ECC errors. Your numbers would work out to 800 MB RAM per job.

Thinking about it some more today, I have for sysctl.conf, because I also run PostgreSQL on the build box (https://www.postgresql.org/docs/current/kernel-resources.html#LINUX-MEMORY-OVERCOMMIT):

vm.swappiness=1

vm.overcommit_memory=2

with vm.overcommit_ratio = 50 as default. I think this is the culprit. Maybe llvm/clang doing insane malloc()s which they never utilize. I set vm.overcommit_memory=0 and am trying again to see what happens.

Anyway thanks for keeping this package up-to-date. Privacy matters.

qcasey commented on 2021-03-15 21:04 (UTC)

@eimis

If you mean getting Chromium to respect the GTK dark theme or prefers-color-scheme, I had to patch this issue for myself. Here's how:

https://github.com/qcasey/chromium-patches#gtk-dark-theme

eimis commented on 2021-03-15 20:58 (UTC)

any way to enable dark mode in settings page and everywhere else?

JstKddng commented on 2021-03-15 20:29 (UTC)

@bsdice

maybe your server has bad ram (?

The OBS with 16GB of ram and 18 parallel jobs finishes without a problem.

bsdice commented on 2021-03-15 20:19 (UTC) (edited on 2021-03-15 20:23 (UTC) by bsdice)

I scratched my itch and made a patch for PKGBUILD: https://pbot.rmdir.de/4aOfwx2X1ftFGqVusX_VHw

Public domain. Will be deleted in 30 days from the server.

Since 10 parallel jobs (ninja calculates 8 threads + 2) failed with 48 GB available, I limit parallel jobs now to "RAM available"/7000, which gives me 6 jobs right now. "Empty" Linux boxes with 16 GB of RAM should run with 2 parallel jobs. Anything below 7000 MB of RAM available will result in a single "good-luck-dude" ninja job, instead of 2 or 3 parallel jobs with 1 or 2 core machines. So it may again work if that guy's Core2 machine has 4/8 GB RAM and 8 GB swap file or swap partition.

Alternatively you can define NINJAFLAGS="-j1" or similar in /etc/makepkg.conf to statically set ninja's parallel job count. In this case no heuristic is used.

bsdice commented on 2021-03-15 18:28 (UTC)

Hey JstKddng and fellow Ungooglers:

I am getting LLVM out of memory errors now too with latest PKGBUILD. I am on a 4C/8T Xeon E3 with 64 GB of RAM. As mentioned here by others MAKEFLAGS is ignored by ninja. My machine is not running empty Linux though. I run 8 GB Swap into zRAM, ZFS (ARC limited to 4 GB), and a bunch of containers but free says 48 GB available right now after aborted makepkg.

I have a hunch this OOM breakage will continue in the future. This is one of the nastiest packages to compile after all in the Archlinux universe.

Could this be automated into a heuristic in PKGBUILD? One that takes "Available" from /usr/bin/free output and if no NINJAFLAGS is available, adjusts the allowed compile processes depending how much memory is currently available. From 1 to floor(AvailableMB / 8000) allowed processes, whichever is higher. Looks to me as if 6000 MB per process is no longer good enough? Ninja's default according to https://github.com/ninja-build/ninja/issues/1441https://github.com/ninja-build/ninja/issues/1441 appears to be CPU Threads + 2.

Hit me up if you think this could work and are open to a patch suggestion.

Intel VAAPI users should also put --enable-features=VaapiVideoDecoder into their chromium-flags.conf because latest version changed things. Hat tip to foutrelis for digging that one up https://bbs.archlinux.org/viewtopic.php?pid=1961399#p1961399

Also only a couple more funny RCEs in this package and I think we should rename it ungoogled-exchange. /s

Thanks!

JstKddng commented on 2021-03-14 02:49 (UTC)

Be sure to update as this release fixes some cves being actively exploited.

BachoSeven commented on 2021-02-09 14:25 (UTC)

@FatBantha

Have a look at the first pinned comment for pre-compiled binaries of this very package, they are always up to date.

FatBantha commented on 2021-02-09 12:52 (UTC)

How much diskspace and memory do I need, to compile Ungoogled Chromium?

I've got barely 4GB of RAM and usually something about 40GB of free space on my legacy Intel Core 2 Duo PC - and that's one of my reasons for choosing UC as a very light browser. Unfortunetely, while the browser itself works perfectly fine, the process of making it is extremely cumbersome if not impossible on older PCs.

Currently, I'm using ungoogled-chromium-appimage, but it's often even more delayed in its package development cycle, just like binaries on site and that's a bit worrying from security/patching standpoint.

Is there a way to compile Ungoogled Chromium on my config?

JstKddng commented on 2021-02-07 04:33 (UTC)

@dr460nf1r3

yeah, that is a problem with glibc, next release will have a patch for that.

« First ‹ Previous 1 .. 21 22 23 24 25 26 27 28 29 30 31 .. 66 Next › Last »