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: 353
Popularity: 4.27
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 2 3 4 5 6 7 .. 66 Next › Last »

lahwaacz commented on 2024-05-19 09:22 (UTC) (edited on 2024-05-19 10:15 (UTC) by lahwaacz)

The following warning is repeated many times during the build:

In file included from <built-in>:455:
<command line>:81:9: warning: '_FORTIFY_SOURCE' macro redefined [-Wmacro-redefined]
   81 | #define _FORTIFY_SOURCE 3
      |         ^
<command line>:9:9: note: previous definition is here
    9 | #define _FORTIFY_SOURCE 2
      |         ^
1 warning generated.

Edit: and the build failed...

FAILED: obj/chrome/browser/extensions/extensions/chrome_file_system_delegate.o
clang++ -MD -MF obj/chrome/browser/extensions/extensions/chrome_file_system_delegate.o.d [......]
In file included from <built-in>:455:
<command line>:95:9: warning: '_FORTIFY_SOURCE' macro redefined [-Wmacro-redefined]
   95 | #define _FORTIFY_SOURCE 3
      |         ^
<command line>:8:9: note: previous definition is here
    8 | #define _FORTIFY_SOURCE 2
      |         ^
In file included from ../../chrome/browser/extensions/api/file_system/chrome_file_system_delegate.cc:16:
../../chrome/browser/download/chrome_download_manager_delegate.h:29:10: fatal error: 'components/safe_browsing/content/common/proto/download_file_types.pb.h' file not found
   29 | #include "components/safe_browsing/content/common/proto/download_file_types.pb.h"
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 warning and 1 error generated.

rabcor commented on 2024-05-07 05:58 (UTC) (edited on 2024-05-07 05:59 (UTC) by rabcor)

in 124 ozone-platform-hint=wayland is broken.

To run on native wayland you gotta use 

chromium --ozone-platform=wayland

BarkleyIII commented on 2024-04-08 20:12 (UTC)

Adding -target x86_64-unknown-linux-gnu to CFLAGS and CXXFLAGS in the PKGBUILD seems to work as a workaround.

BarkleyIII commented on 2024-03-30 15:01 (UTC)

Im getting the same linking errors as randomnobody, but so far nothing I tried helped. My makepkg.conf does not seem to be the problem, at least as far as I can tell. There isn't a .pacnew version either. Any help or pointers to further diagnose the problem would be very welcome.

randomnobody commented on 2024-03-22 01:19 (UTC)

Self resolved. I believe my error was related to my makepkg.conf, which I hadn't updated from the .pacnew. If you have the same issues try defaulting your settings.

randomnobody commented on 2024-03-20 06:19 (UTC)

I'm getting linking errors because my C/C++ objects are targeting x86_64-pc-linux-gnu and rust is targeting x86_64-unknown-linux-gnu. rustc doesn't even seem to support x86_64-pc-linux-gnu as valid target. See example below.

ld.lld: error: Linking two modules of different target triples: 'obj/base/nodebug_assertion/nodebug_assertion.o' is 'x86_64-pc-linux-gnu' whereas 'obj/components/qr_code_generator/libcomponents_sqr_ucode_ugenerator_cqr_ucode_ugenerator_uffi_uglue.rlib(libcomponents_sqr_ucode_ugenerator_cqr_ucode_ugenerator_uffi_uglue.components_sqr_ucode_ugenerator_cqr_ucode_ugenerator_uffi_uglue.93cc98de3648a0e9-cgu.0.rcgu.o at 8722)' is 'x86_64-unknown-linux-gnu'

jahway603 commented on 2024-02-05 13:40 (UTC)

Build fails as it appears REVERT-simplify-blink-NativeValueTraitsBase.patch ... FAILED has changed.

« First ‹ Previous 1 2 3 4 5 6 7 .. 66 Next › Last »