Package Details: ungoogled-chromium 137.0.7151.103-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: 354
Popularity: 1.01
First Submitted: 2016-12-19 08:08 (UTC)
Last Updated: 2025-06-11 19:56 (UTC)

Required by (143)

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 .. 34 35 36 37 38 39 40 41 42 43 44 .. 67 Next › Last »

<deleted-account> commented on 2020-05-05 10:14 (UTC)

@Megumi_fox I know, It has additional VAAPI patches that doesn't exist in this AUR. Its actually a combination of this package and chromium-vaapi. I personally need those patches to make VAAPI work and I don't know why those patches weren't added in ungoogled-chromium-archlinux github repo.

Megumi_fox commented on 2020-05-05 09:14 (UTC)

@Rowisi this package in ArchlinuxCN is not maintained by Felix Yan. And PKGBUILD has difference between ArchlinuxCN and AUR, more detail can see here

<deleted-account> commented on 2020-05-05 07:51 (UTC)

If someone failed to compile this package he can use ArchlinuxCN It is maintained by a group of people including Felix Yan an Archlinux developper.

neeks commented on 2020-05-05 06:43 (UTC)

good catch @volfyd and apologizes @jfk -- wrote it post-fail and didn't realize the original I was patching had domain-substitutions already applied

volfyd commented on 2020-05-05 00:59 (UTC) (edited on 2020-05-05 01:37 (UTC) by volfyd)

@jfk, if you edit the @neeks patch changing the line

 // See https://bugs.chromium.org/p/v8/issues/detail?id=8641

to

 // See https://bugs.ch40m1um.qjz9zk/p/v8/issues/detail?id=8641

it should apply, and I just managed to recompile chromium with that patch successfully.

<deleted-account> commented on 2020-05-04 23:58 (UTC)

@nathanielcwm Nice, I didn't know that was possible with makepkg.

nathanielcwm commented on 2020-05-04 12:32 (UTC) (edited on 2020-05-04 12:36 (UTC) by nathanielcwm)

makepkg -e stops it from extracting I think

Just checked and it also bypasses the prepare() section.

<deleted-account> commented on 2020-05-04 11:28 (UTC)

I am starting to think that we have to add another PKGBUILD file let's called PKGBUILD.resume for people who want to continue building if the build crashed or when they stopped the build.

Its so easy just remove all prepare() { ... } function and add 

noextract=("chromium-$pkgver.tar.xz"
           "v$_launcher_ver.tar.gz")

when someone wants to resume building, he just have to do cat PKGBUILD.resume > PKGBUILD and continue building chromium.

<deleted-account> commented on 2020-05-04 04:14 (UTC)

@volfyd 1- I mean its better to upgrade chromium than downgrading libraries.

2- No, you must upgrade your Chromium to fix the vulnerability.

volfyd commented on 2020-05-04 03:05 (UTC)

@Rowisi I was talking about downgrading the libraries that were causing problems and not Chromium itself. Are you saying that the libraries are involved in the use after free issue you mention?

« First ‹ Previous 1 .. 34 35 36 37 38 39 40 41 42 43 44 .. 67 Next › Last »