Package Details: ungoogled-chromium 124.0.6367.60-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: seppia (JstKddng)
Last Packager: JstKddng
Votes: 343
Popularity: 4.57
First Submitted: 2016-12-19 08:08 (UTC)
Last Updated: 2024-04-24 04:38 (UTC)

Required by (119)

Sources (12)

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 .. 3 4 5 6 7 8 9 10 11 12 13 .. 64 Next › Last »

JstKddng commented on 2022-06-23 12:21 (UTC)

@whitecatkeke

indeed, the patch that was being used fails in this version of chromium

whitecatkeke commented on 2022-06-23 12:18 (UTC)

It seems hardware acceleration stopped working after today's update on Wayland?

JstKddng commented on 2022-05-19 15:59 (UTC)

@dadude1

Those flags are only needed if you are using wayland

dadude1 commented on 2022-05-19 13:25 (UTC) (edited on 2022-05-19 15:45 (UTC) by dadude1)

Hello everyone, I am sorry to ask but where I have to write this so ungoogled Chromium is working again: --disable-features=UseChromeOSDirectVideoDecoder --disable-gpu-memory-buffer-compositor-resources --disable-gpu-memory-buffer-video-frames --enable-hardware-overlays

I am a noob, I tried in the terminal. Chrome does not start at all at the moment. Thanks for your help

JstKddng commented on 2022-05-16 15:13 (UTC)

@pdpelf

icu was updated to 71.1 a long time ago, maybe you are using an outdated mirror.

pdpelf commented on 2022-05-16 09:23 (UTC)

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

Since last update, ICU is now at: libicui18n.so.71.1

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

smokeinbrain commented on 2022-04-29 10:44 (UTC)

@fcolecumberri i don't seem to have that flag in my /etc/makepkg.conf file...

fcolecumberri commented on 2022-04-26 22:56 (UTC)

the -fvar-tracking-assignments problem can be solved by removing that flag from the /etc/makepkg.conf file (which makes sense since it's a g++ only flag and ungoogled-chromium uses clang++ to compile).

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 64 Next › Last »