Package Details: ungoogled-chromium 145.0.7632.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: 359
Popularity: 0.63
First Submitted: 2016-12-19 08:08 (UTC)
Last Updated: 2026-03-04 22:59 (UTC)

Required by (165)

Sources (9)

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

1 2 3 4 5 6 .. 69 Next › Last »

norbert79 commented on 2026-02-21 08:23 (UTC) (edited on 2026-02-21 08:24 (UTC) by norbert79)

Hi there,

your latest update has a wrong link in the package (or the GitHub listing has been created bad), so it means, that your package wants to download the latest package 145.0.7632.109-2 from : https://github.com/ungoogled-software/ungoogled-chromium-archlinux/releases/download/145.0.7632.109-2/ungoogled-chromium-145.0.7632.109-2-x86_64.pkg.tar.zst

but the actual GitHub link is pointing to: https://github.com/ungoogled-software/ungoogled-chromium-archlinux/releases/download/145.0.7632.109-1/ungoogled-chromium-145.0.7632.109-2-x86_64.pkg.tar.zst

So in the GitHub link the link has 145.0.7632.109-1 in it, despite pointing to ungoogled-chromium-145.0.7632.109-2-x86_64.pkg.tar.zst, yours is trying to point to the most logical one of 145.0.7632.109-2/145.0.7632.109-2. Minor issue, just a mistake from the GitHub maintainer side, but wanted to point out.

emceebois commented on 2026-02-05 14:22 (UTC) (edited on 2026-02-05 14:22 (UTC) by emceebois)

Getting the following error when running makepkg:

[user@badvertising-ll ungoogled-chromium]$ makepkg -csi
==> Making package: ungoogled-chromium 144.0.7559.132-1 (Thu 05 Feb 2026 09:21:24 AM EST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found fetch-chromium-release
  -> Found ungoogled-chromium-144.0.7559.132-1.tar.gz
  -> Found chromium-launcher-8.tar.gz
  -> Found compiler-rt-adjust-paths.patch
  -> Found increase-fortify-level.patch
  -> Found use-oauth2-client-switches-as-default.patch
  -> Found 0001-adjust-buffer-format-order.patch
  -> Found 0001-enable-linux-unstable-deb-target.patch
  -> Found 0001-ozone-wayland-implement-text_input_manager_v3.patch
  -> Found 0001-ozone-wayland-implement-text_input_manager-fixes.patch
  -> Found 0001-vaapi-flag-ozone-wayland.patch
  -> Found chromium-138-nodejs-version-check.patch
==> Validating source files with sha256sums...
    fetch-chromium-release ... FAILED
    ungoogled-chromium-144.0.7559.132-1.tar.gz ... Passed
    chromium-launcher-8.tar.gz ... Passed
    compiler-rt-adjust-paths.patch ... Passed
    increase-fortify-level.patch ... Passed
    use-oauth2-client-switches-as-default.patch ... Passed
    0001-adjust-buffer-format-order.patch ... Passed
    0001-enable-linux-unstable-deb-target.patch ... Passed
    0001-ozone-wayland-implement-text_input_manager_v3.patch ... Passed
    0001-ozone-wayland-implement-text_input_manager-fixes.patch ... Passed
    0001-vaapi-flag-ozone-wayland.patch ... Passed
    chromium-138-nodejs-version-check.patch ... Passed
==> ERROR: One or more files did not pass the validity check!

Vergenter commented on 2026-01-29 00:55 (UTC) (edited on 2026-01-29 01:02 (UTC) by Vergenter)

Build failure: ESLint plugin uses Set.prototype.intersection (requires newer Node)

ESLint: 9.20.1

TypeError: importedFilenames.intersection is not a function
Occurred while linting <REDACTED>/.cache/makepkg/build/ungoogled-chromium/src/chromium-144.0.7559.109/out/Release/gen/ui/webui/resources/cr_components/search/preprocessed/animated_glow.html.ts:10

Set.prototype.intersection is not available on Node 20 (needs newer Node / newer JS runtime support), so the lint step crashes and Ninja aborts.

Fix options:

  1. Preferred: bump build dependency / enforce newer Node for the lint step
  2. Workaround: polyfill/patch intersection in the plugin

Simply pasting it into webui_eslint_plugin.js below headers, specifically under const POLYMER_IMPORT_REGEX fixed it for me:

if (!Set.prototype.intersection) {
  // eslint-disable-next-line no-extend-native
  Set.prototype.intersection = function (other) {
    const otherSet = other instanceof Set ? other : new Set(other);
    const out = new Set();
    for (const v of this) {
      if (otherSet.has(v)) out.add(v);
    }
    return out;
  };
}

emceebois commented on 2026-01-26 01:04 (UTC)

Now getting an error when trying to clean build: https://pastebin.com/kR9bYJjy

nich23 commented on 2026-01-12 20:40 (UTC)

Aarch64 architecture


../../third_party/libyuv/source/row_sme.cc:231:30: error: function executed in streaming-SVE mode requires 'sme'
  231 | __arm_locally_streaming void YUY2ToARGBRow_SME(
      |                              ^
../../third_party/libyuv/source/row_sme.cc:239:30: error: function executed in streaming-SVE mode requires 'sme'
  239 | __arm_locally_streaming void UYVYToARGBRow_SME(
      |                              ^
../../third_party/libyuv/source/row_sme.cc:247:30: error: function executed in streaming-SVE mode requires 'sme'
  247 | __arm_locally_streaming void I210ToARGBRow_SME(
      |                              ^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
[2983/54374] CC obj/third_party/sqlite/chromium_sqlite3/sqlite3_shim.o
ninja: build stopped: subcommand failed.
==> ERROR: A failure occurred in build().
    Aborting...

Wennadocta commented on 2025-11-25 17:43 (UTC)

Looks like my building processes were killed by OOM. I increased the RAM available for my building VM and it now builds fine. I think you need >32GB of RAM to build it successfully

graysky commented on 2025-11-25 13:52 (UTC)

I built ungoogled-chromium-142.0.7444.175-1 on 21-Nov with ccm just fine/have not tried since.

Wennadocta commented on 2025-11-25 13:37 (UTC)

So, after the latest update (142.0.7444.175-1) I get these compilation errors I build it in a clean chroot using the script ccm

the error log is HUGE so I attach it with pastebin: https://pastebin.com/raw/dhJgcJct

it starts with FAILED: [code=137] obj/content/browser/browser/browser_interface_binders.o

What can cause it? Does it compile for you?

Wennadocta commented on 2025-11-03 20:29 (UTC)

Can confirm that it builds in clean chroot, thanks for this script

graysky commented on 2025-11-02 09:36 (UTC)

@Wennadocta - Not the same. Try in a clean build root and report back. https://aur.archlinux.org/packages/clean-chroot-manager

1 2 3 4 5 6 .. 69 Next › Last »