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: 354
Popularity: 5.02
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 .. 60 61 62 63 64 65 66 Next › Last »

PerfectGentleman commented on 2016-09-06 15:44 (UTC)

-Dremoting=0 -Dsafe_browsing=0 are right switches, not those in PKGBUILD

dreieck commented on 2016-07-30 07:42 (UTC)

Fails to apply patches (though sources pass the checksum tests): == %< == ==> Starting prepare()... can't find file to patch at input line 4 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |diff -upr chromium-48.0.2564.82.orig/chrome/common/chrome_content_client.cc chromium-48.0.2564.82/chrome/common/chrome_content_client.cc |--- chromium-48.0.2564.82.orig/chrome/common/chrome_content_client.cc 2016-01-20 22:01:20.000000000 +0200 |+++ chromium-48.0.2564.82/chrome/common/chrome_content_client.cc 2016-01-21 20:02:02.788936626 +0200 -------------------------- File to patch: can't find file to patch at input line 21 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |diff -upr chromium-48.0.2564.82.orig/chrome/common/chrome_paths.cc chromium-48.0.2564.82/chrome/common/chrome_paths.cc |--- chromium-48.0.2564.82.orig/chrome/common/chrome_paths.cc 2016-01-20 22:01:20.000000000 +0200 |+++ chromium-48.0.2564.82/chrome/common/chrome_paths.cc 2016-01-21 19:18:51.287978456 +0200 -------------------------- File to patch: can't find file to patch at input line 36 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |diff -upr chromium-48.0.2564.82.orig/chrome/common/chrome_paths.h chromium-48.0.2564.82/chrome/common/chrome_paths.h |--- chromium-48.0.2564.82.orig/chrome/common/chrome_paths.h 2016-01-14 03:49:22.000000000 +0200 |+++ chromium-48.0.2564.82/chrome/common/chrome_paths.h 2016-01-21 19:18:51.287978456 +0200 -------------------------- File to patch: == >% ==

c0d3x commented on 2016-07-01 23:00 (UTC) (edited on 2016-07-01 23:04 (UTC) by c0d3x)

==> Starting build()... sed \ -e "s|@CHROMIUM_NAME@|inox|g" \ -e "s|@CHROMIUM_BIN@|/usr/lib/inox/inox|g" \ -e "s|@PEPPER_FLASH_DIR@|/usr/lib/PepperFlash|g" \ -e "s|@LAUNCHER_ERRMSG@|/usr/lib/inox-launcher/launcher-errmsg|g" \ chromium-launcher.in >inox-launcher cc -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -std=c99 -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/pango-1.0 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro launcher-errmsg.c -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lfontconfig -lfreetype -o launcher-errmsg Updating projects from gyp files... ninja: Entering directory `out/Release' ninja: error: '../../native_client/toolchain/linux_x86/pnacl_newlib/pnacl_newlib.json', needed by 'gen/tc_irt/lib64/libppapi_proxy_nacl.a', missing and no known rule to make it ==> ERROR: A failure occurred in build(). Aborting...

timofonic commented on 2016-06-01 19:52 (UTC)

Is it possible to enable NPAPI?

gcarq commented on 2016-03-30 17:28 (UTC)

@Peter1992 No it's not dead. I'm just quite busy these days.

Peter1992 commented on 2016-03-28 15:28 (UTC) (edited on 2016-03-28 15:28 (UTC) by Peter1992)

@gcarq What happened to this package? Is it dead or do you not have that much time to work on it anymore?

gcarq commented on 2016-03-03 17:19 (UTC)

I've added libvpx. You got me ;) I think have to improve my build env

sekret commented on 2016-02-22 10:19 (UTC)

You need to add libvpx to makedepends. I tried to build inox in a clean chroot according to https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_Clean_Chroot and here's where it fails ==> Starting build()... sed \ -e "s|@CHROMIUM_NAME@|inox|g" \ -e "s|@CHROMIUM_BIN@|/usr/lib/inox/inox|g" \ -e "s|@PEPPER_FLASH_DIR@|/usr/lib/PepperFlash|g" \ -e "s|@LAUNCHER_ERRMSG@|/usr/lib/inox-launcher/launcher-errmsg|g" \ chromium-launcher.in >inox-launcher cc -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -std=c99 -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/pango-1.0 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro launcher-errmsg.c -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lfontconfig -lfreetype -o launcher-errmsg Updating projects from gyp files... Package vpx was not found in the pkg-config search path. Perhaps you should add the directory containing `vpx.pc' to the PKG_CONFIG_PATH environment variable No package 'vpx' found gyp: Call to 'pkg-config --cflags vpx' returned exit status 1 while in /build/inox/src/chromium-48.0.2564.82/third_party/libvpx_new/libvpx.gyp. ==> ERROR: A failure occurred in build(). Aborting... I didn't build it completely, but according to namcap it's no dependency, so I think it's a makedependency. Don't you build inox-bin in a clean chroot?? ;-)

sekret commented on 2015-09-03 17:43 (UTC)

44.0.2403.157-1 built fine, but 45.0.2454.85 has many changes, so the patches don't work anymore.

sekret commented on 2015-08-20 20:10 (UTC)

Tried to build this version and the version of [extra]'s chromium, both fail like this http://codepad.org/0Fvqj2wQ I only changed _build_nacl=0 on my 64bit machine. Can this be the reason?

« First ‹ Previous 1 .. 60 61 62 63 64 65 66 Next › Last »