Package Details: ungoogled-chromium 131.0.6778.204-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: 3.99
First Submitted: 2016-12-19 08:08 (UTC)
Last Updated: 2024-12-20 12:47 (UTC)

Dependencies (49)

Required by (135)

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 8 9 10 11 .. 66 Next › Last »

xAsh commented on 2023-03-09 22:46 (UTC)

updating ffmpeg to the latest version broke the required shared libraries (libavcodec.so.59, libavformat.so.59, libavutil.so.57)

JstKddng commented on 2023-02-28 15:55 (UTC)

@cmonty14

you can build on /tmp. You'd need at least 32gb and don't use all your cores otherwise you'll run out of memory.

cmonty14 commented on 2023-02-28 14:56 (UTC)

Is there any option to accelerate the build process except for adding CPU cores?

JstKddng commented on 2023-01-16 01:53 (UTC)

@randomnobody

are you perhaps building directly in your ram? as in, building in /tmp? If there was indeed such a jump, the OBS build would certainly fail as the workers don't have that much memory.

randomnobody commented on 2023-01-16 00:01 (UTC) (edited on 2023-01-17 02:53 (UTC) by randomnobody)

With the new 109 update, the final linking stages of chromium ld.lld consumes approximately 70GB of memory and then proceeds to grind on swap memory until I give up and cancel the job. Is this expected behavior? 108 and prior could generally fit within 32GB of memory, is there a reason for a sudden explosion of memory usage during linking?

EDIT: I was able to successfully build after removing -flto from my makepkg.conf CFLAGS. I also did the build under a fresh user in case some part of my home dir was impacting the build.

missingSleepDeps commented on 2022-12-10 07:05 (UTC)

Thanks, but it managed to build successfully after I gave up on using cpulimit to keep the build from freezing the desktop...

jronald commented on 2022-12-10 05:44 (UTC) (edited on 2022-12-22 13:25 (UTC) by jronald)

@missingSleepDeps

The patch file shows the file to patch, e.g. src/chromium-108.0.5359.94/build/config/compiler/BUILD.gn

I did it after prepare() manually, so I splitted PKGBUILD here.

It's also ok to be appended to the end of prepare() in PKGBUILD,

BTW the patch file should end with a single new line, or it can't be applied.

missingSleepDeps commented on 2022-12-10 05:12 (UTC)

@jronald apply patch where and how?

jronald commented on 2022-12-08 16:41 (UTC) (edited on 2022-12-09 05:20 (UTC) by jronald)

@Wilco

After applying the patch below, it succeeds.

--- a/build/config/compiler/BUILD.gn
+++ b/build/config/compiler/BUILD.gn
@@ -589,15 +589,6 @@
       if (is_clang) {
         cflags_cc += [ "-fno-trigraphs" ]
       }
-    } else if (is_linux) {
-      # TODO(crbug.com/1284275): Switch to C++20 on all platforms.
-      if (is_clang) {
-        cflags_cc += [ "-std=${standard_prefix}++20" ]
-      } else {
-        # The gcc bots are currently using GCC 9, which is not new enough to
-        # support "c++20"/"gnu++20".
-        cflags_cc += [ "-std=${standard_prefix}++2a" ]
-      }
     } else {
       cflags_cc += [ "-std=${standard_prefix}++17" ]
     }
@@ -611,12 +602,7 @@
     # turned off we need the !is_nacl clause and the (is_nacl && is_clang)
     # clause, above.
     cflags_c += [ "-std=c11" ]
-    if (is_mac) {
-      # TODO(crbug.com/1284275): Switch to C++20 on all platforms.
-      cflags_cc += [ "-std=c++20" ]
-    } else {
       cflags_cc += [ "-std=c++17" ]
-    }
   }

   if (is_clang && current_os != "zos") {

I've not tried clang 15

Wilco commented on 2022-12-08 09:24 (UTC)

@jronald

Thanks but this is incorrect. I just managed to successfully compile ungoogled chromium with clang 14. The solution is recompiling llvm, clang, compiler-rt and lld. I think there is a circular dependency requiring to build the packages twice before they work correctly.

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