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

JstKddng commented on 2020-11-28 01:13 (UTC)

@lahwaacz

Huh, interesting. Well, I could just pass the MAKEFLAGS variable to ninja, assuming it only contains the j flag.

lahwaacz commented on 2020-11-27 23:38 (UTC) (edited on 2020-11-27 23:44 (UTC) by lahwaacz)

ninja understands -j just like make, but ninja does not use $MAKEFLAGS. Also, ninja uses the number of logical CPUs available on the system as the maximum number of parallel jobs by default, so there is no point in specifying -j $(nproc). But, in case of Chromium, the high number of parallel jobs is exactly what is causing issues for people who don't have enough RAM. As I said several times here, they should try to lower the maximum number of parallel jobs to avoid mysterious errors as well as a slow(er) build with enabled swap.

Note that unlike ninja, make uses -j 1 by default. While ninja does not have anything like $MAKEFLAGS, but some packages like llvm-git introduce a similar variable to make things configurable:

There is also some discussion about it in the comments, see 2019-04-28 14:08 and before.

JstKddng commented on 2020-11-27 23:25 (UTC)

@lahwaacz

Really? I thought ninja recognized that flag. Oh well, the more you know. I could add a -j flag to ninja, but that won't always be the best value for every computer, -j $(nproc) I think would be a good value.

lahwaacz commented on 2020-11-27 20:44 (UTC)

@JstKddng MAKEFLAGS affect GNU make, not ninja. They can modify the PKGBUILD to pass -j whatever directly to ninja.

JstKddng commented on 2020-11-27 20:22 (UTC)

@bkb

If you want to change default behaviour modify the /etc/makepkg.conf file and modify the MAKEFLAGS flag to this: MAKEFLAGS="-j9"

Replace 9 by the number of threads on your system + 1. That should work with all packages you update with yay- Syu.

@lahwaacz @boomerdango

Good to know the flags work. Thanks for the feedback.

lahwaacz commented on 2020-11-27 17:50 (UTC)

@boomerdango Thanks, I can confirm those flags work with ungoogled-chromium under Sway.

bkb commented on 2020-11-27 15:55 (UTC)

The question was about checking default execution, not forcing it

boomerdango commented on 2020-11-27 15:52 (UTC) (edited on 2020-11-27 15:52 (UTC) by boomerdango)

@lahwaacz It works natively if you launch it with --enable-features=UseOzonePlatform --ozone-platform=wayland, or put those flags in your ~/.config/chromium-flags.conf.

lahwaacz commented on 2020-11-24 19:24 (UTC)

@JstKddng It has worked under Wayland before, thanks to XWayland. Is there a way to check the native support (other than disabling XWayland completely)?

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