Package Details: ungoogled-chromium 76.0.3809.132-1

Git Clone URL: https://aur.archlinux.org/ungoogled-chromium.git (read-only)
Package Base: ungoogled-chromium
Description: A lightweight approach to removing Google web service dependency
Upstream URL: https://github.com/Eloston/ungoogled-chromium
Keywords: blink browser privacy web
Licenses: BSD
Conflicts: chromium
Provides: chromium
Submitter: ilikenwf
Maintainer: seppia
Last Packager: seppia
Votes: 104
Popularity: 5.776331
First Submitted: 2016-12-19 08:08
Last Updated: 2019-09-06 12:15

Dependencies (53)

Required by (49)

Sources (4)

Pinned Comments

seppia commented on 2019-04-07 18:31

There have been made some changes in ungoogled-chromium and there now is a separate git repository handling archlinux packaging and building. There are some concerns about the decisions that must be done reguarding the versioning scheme in paritcular. You could read about it in details here https://github.com/ungoogled-software/ungoogled-chromium-archlinux/issues/1 . I've always followed upstream versioning because that was ideal, also for AUR PKGBUILD, but now, as already stated, some concerns have been risen. I'm honestly a bit confused and it's not very clear to me which solution would be better to adopt. I would like to know your opinion in merit, what this community thinks about it and I encourage and very much appreciate any direct involvement from anyone interested on github repo and issue.

seppia commented on 2018-12-12 21:34

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

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

NullRoute commented on 2019-09-15 14:29

@ seppia - Please make proper ungoogled-chromium-bin with latest version. Thank you!

devnoname120 commented on 2019-09-15 13:03

My bad, I meant to post this comment in https://aur.archlinux.org/packages/ungoogled-chromium-bin/.

Scrumplex commented on 2019-09-15 12:59

@devnoname120 you need to recompile ungoogled-chromium

devnoname120 commented on 2019-09-15 12:48

I have the following error when starting Chromium:

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

It happens because the listed dependency (jsoncpp) doesn't have the same version as the one ungoogled-chromium was compiled against.

slondr commented on 2019-08-12 15:52

"patch: unrecognized option '--igonre-whitespace'"

Seems like there's a typo in one of the patch commands. This is preventing install for me.

JstKddng commented on 2019-08-11 00:58

@bsdice

well, I got those flags from the wiki and they work for me (and yes, most of those flags aren't in chrome://flags, don't sweat it), just use whatever works for you.

bsdice commented on 2019-08-11 00:36

@JstKddng Thank you! Your version is the best working VAAPI-enabled ungoogled chromium. I'd love to see your version in official AUR.

After compile I did a brief CPU load test using a random Youtube video in 1080p/50fps, rendered to a 1080p 60fps screen. CPU was a fanless Pentium Silver N5000 with 6W TDP (Acer Swift 1, model SF114-32, stock 8GB RAM 256GB SSD). I have kernel.unprivileged_userns_clone=1 active to enable native sandboxing, also using i3 on X11, modesetting driver, libva-intel-driver (intel-media-driver appears to have seeking problems still).

The CPU pretty much stays at the base clock of 1100 MHz all the time, although it could burst to 2700 MHz if necessary. Various chromium processes were using around 60% of one core in total. So pretty decent headroom here.

The only value in chromium-flags.conf necessary was --ignore-gpu-blacklist, dark mode stuff aside. Everything else led to glitches, did not exist in chrome://flags, or did not lower CPU load in any for me discernable way.

JstKddng commented on 2019-08-10 19:22

@thefallenrat

Are you compiling the new version Eloston bumped? It is working for me. I'm using a different pkgbuild though, check it out in my github repo:

https://github.com/jstkdng/ungoogled-chromium-archlinux

thefallenrat commented on 2019-08-10 13:11

EDIT EDIT: The build works with added is_official_build=false flag

EDIT: Nvm the build failed

@seppia, please update your _archver variable to the latest commit of the project as it contains some removal of flags that will surely fix crashes on startup. See below for details: https://github.com/ungoogled-software/ungoogled-chromium-archlinux/issues/22

Also, please don't use $pkgver reference in your ungoogled_repo variable. Cause I find it annoying that when I try to bump pkgrel, I have to switch all $pkgver reference to $_rev

JstKddng commented on 2019-08-09 23:23

Can confirm, the new vaapi patch from ungoogled-chromium is causing the crashes. The vaapi patch from chromium-vaapi works as expected. The only option would be to remove the vaapi patch and recompile. That's why I haven't released a new version for my repo.

Edit:

nope, still the same problem, Illegal instruction. We'll have to wait for Eloston now.