Package Details: ungoogled-chromium 132.0.6834.159-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: 2.87
First Submitted: 2016-12-19 08:08 (UTC)
Last Updated: 2025-01-29 23:47 (UTC)

Dependencies (49)

Required by (135)

Sources (11)

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 .. 13 14 15 16 17 18 19 20 21 22 23 .. 67 Next › Last »

JstKddng commented on 2021-11-18 17:22 (UTC)

@followait

You can try updating and checking if that error persists, though, I think that error is on the window manager side, not chromium's. Under awesomewm it does remember the size before closing.

@aemonge

Clean the srcdir

followait commented on 2021-11-05 22:11 (UTC) (edited on 2021-11-06 13:15 (UTC) by followait)

Env
  • manjaro: x86-64 2021/11/05
  • ungoogled-chromium: 95.0.4638.69
Reproduce
  1. lauch chromium, let the window be in non-maximum and non-minimum mode, close the window, so chromium will remember the size of the window as default
  2. lauch chromium again, the size of the window is obviously smaller than the size it remembers

aemonge commented on 2021-11-05 14:07 (UTC)

Any idea how to fix this issue? 

Traceback (most recent call last):
  File "/home/aemonge/lib/ungoogled-chromium/src/ungoogled-chromium-95.0.4638.69-1/utils/patches.py", line 250, in <module>
    main()
  File "/home/aemonge/lib/ungoogled-chromium/src/ungoogled-chromium-95.0.4638.69-1/utils/patches.py", line 246, in main
    args.callback(args, parser.error)
  File "/home/aemonge/lib/ungoogled-chromium/src/ungoogled-chromium-95.0.4638.69-1/utils/patches.py", line 198, in _apply_callback
    apply_patches(
  File "/home/aemonge/lib/ungoogled-chromium/src/ungoogled-chromium-95.0.4638.69-1/utils/patches.py", line 132, in apply_patches
    subprocess.run(cmd, check=True)
  File "/usr/lib/python3.9/subprocess.py", line 528, in run
    raise CalledProcessError(retcode, process.args,

followait commented on 2021-10-31 12:56 (UTC)

@monarc99

"using AVX instructions infrequently could degrade performance or power efficiency"

https://stackoverflow.com/questions/52653025/why-is-march-native-used-so-rarely

monarc99 commented on 2021-10-31 10:33 (UTC)

i use for my private builds on my newer notebook (with avx2 support):

CFLAGS="-march=native -mtune=native -O3 -pipe -fno-plt"

for my old desktop (pre AVX2) pc, i had to switch back to

CFLAGS="-march=x86-64-v2 -mtune=native -O3 -pipe -fno-plt"

there a avx2 instructions in tensorflow (to test, if the cpu support avx2), and the compiler is confused, to compile avx2 instructions, when -march=native disables avx2.

and i enable PGO: in PKGBUILD before the CFLAGS settings:

# enable pgo
_linux_pgo_file=$(cat chrome/build/linux.pgo.txt)
if [ ! -f "chrome/build/pgo_profiles/${_linux_pgo_file}" ]; then
  msg2 'Downloading pgo_profiles data'
  curl "https://storage.googleapis.com/chromium-optimization-profiles/pgo_profiles/${_linux_pgo_file}" --output "chrome/build/pgo_profiles/${_linux_pgo_file}"
fi
_flags+=(
  'chrome_pgo_phase=2'
  'is_clang=true'
  'use_lld=true'
)

lahwaacz commented on 2021-10-31 07:05 (UTC)

and that could hurt performance on intel cpus.

Not only that, it would most likely segfault on other (micro)architectures due to unknown instructions.

JstKddng commented on 2021-10-31 03:26 (UTC)

@followait

you can certainly try adding it to your builds but I wouldn't add it here as the repo builds would be optimized for the architecture the OBS uses for compiling (amd epyc iirc) and that could hurt performance on intel cpus.

followait commented on 2021-10-31 01:51 (UTC) (edited on 2021-10-31 01:52 (UTC) by followait)

For GCC and clang, what about adding option "-march=native", which also implies "-mtune=native"?

How much performance can it boost?

RonnyD commented on 2021-10-26 16:52 (UTC)

On one of my devices, I get the following error:

[4041/49178] ACTION //third_party/blink/public/moj...sage_ids(//build/toolchain/linux/unbundle:default)ninja: error: WriteFile(__third_party_blink_public_mojom_memory_usage_monitor_linux_mojo_bindings__generate_message_ids___build_toolchain_linux_unbundle_default__rule..rsp): Unable to create file. File name too long

Maybe this could be caused through /tmp being mounted on the drive as opposed to a ramdisk? Versions up 'til 91 installed fine, just fine, though.

Any thoughts?

« First ‹ Previous 1 .. 13 14 15 16 17 18 19 20 21 22 23 .. 67 Next › Last »