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: 352
Popularity: 4.12
First Submitted: 2016-12-19 08:08 (UTC)
Last Updated: 2024-11-20 21:14 (UTC)

Required by (136)

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 .. 43 44 45 46 47 48 49 50 51 52 53 .. 66 Next › Last »

bsdice commented on 2020-01-07 04:02 (UTC)

Will you stick to ungoogled-chromium no matter what?

@MasterOne

Sorry for late reply, somehow I missed your question. I will stick to ungoogled-chromium because a) chromium code base is the most aggressively security-bugfixed browser today b) since Edge browser will switch to chromium's engine(s) under the hood, it will be the browser most sites will optimize for and be compatible with going forward c) hardware accelerated video for H.264/H.265 d) paranoid privacy of this fork.

My fallback thus far has been Palemoon. If manifest v3 cripples the extensions that I use and want (uBlock Origin, uMatrix, Tampermonkey, Editthiscookie, and some more), and no patches can revive them, I will reconsider. Pure Firefox is out of the question, the Mozilla organisation is pretty much governed by money and can't be trusted. IMO they're fed ad dollars by Google only to have a 'competitor' on paper, should congress turn nasty on Google in an anti-trust case.

I saw Fabrice Bellard has single-handedly written "QuickJS", a MIT-licensed javascript engine. Maybe a whole new browser with 1/20th the code base of chromium will appear in the 2020s that uses it. If some super-freaks get together to build one, the market in a world governed by the FAANG companies is certainly there.

settyness commented on 2020-01-07 02:12 (UTC)

@MasterOne The answer is GNU IceCat. If you're serious enough to build the package, you can use provided icecat package here on the AUR. I used to use ungooged-chromium-bin for normie browsing, but that's about it. I honestly wouldn't trust any Chromium derivative these days for everyday browsing. I came here to check on the status of this project, since its binary has been removed from the AUR.

It kinda sucks there isn't a decent option for using normie stuff like workday or bank accounts. You pretty much just have to suck it up and go vanilla Chromium or something else, unless you wanna spend time building this for little gain. Again, GNU/IceCat is great for everyday use and just general browsing where blocking everything is acceptable.

devnoname120 commented on 2020-01-05 17:41 (UTC) (edited on 2020-01-06 11:02 (UTC) by devnoname120)

Install them manually then use https://aur.archlinux.org/packages/chromexup/ to update them.

eimis commented on 2020-01-05 17:12 (UTC)

how do you guys install extensions?

MasterOne commented on 2019-12-02 14:01 (UTC)

@bsdice, yes, this is of big concern!

I am still drawn between the use of Firefox and ungoogled-chromium, and I just can't seem to be able to make up my mind. Will you stick to ungoogled-chromium no matter what?

bsdice commented on 2019-12-02 10:11 (UTC)

To whom it may be of concern:

Chromium, and thus ungoogled-chromium, today has sadly become only a second-class citizen when it comes to blocking web objects from unwanted sources: https://github.com/gorhill/uBlock/commit/3a564c199260a857f3d78d5f12b8c3f1aa85b865

TLDR; The ad industry is abusing a DNS feature to "cloak" their servers, in order to be more difficult to block. Countermeasures require browser support that only Firefox has today. I would hope that a developer can come up with a patch over the holidays that adds the webext API "dns" to ungoogled-chromium. And that Gorhill can implement this as an option for the Chromium version.

Does Google have an interest to not implement this, because they are foremost an ad-company? Sure. Do I not want to execute unknown and malicious javascript on a browser with sub-par security on Intel CPUs with abysmal security track record? For sure. Will 99.9% of users care? Surely not, they eat what Google or Microsoft care to serve.

tpaniaki commented on 2019-11-17 19:54 (UTC)

@seppia @Megumi_fox: thanks for your quick feedback and update. Apparently that was indeed the problem.

seppia commented on 2019-11-17 09:48 (UTC)

@jfk your error (which can't be determined only from the line you pasted here) was probably due to the icu 65 bug in chromium reported here by Megumi_fox. You should now be able to build ungoogled-chromium again.

« First ‹ Previous 1 .. 43 44 45 46 47 48 49 50 51 52 53 .. 66 Next › Last »