Package Details: google-chrome-wayland-vulkan 128.0.6613.137-1

Git Clone URL: https://aur.archlinux.org/google-chrome-wayland-vulkan.git (read-only, click to copy)
Package Base: google-chrome-wayland-vulkan
Description: The popular web browser by Google (Stable Channel) with a binary patch to enable support for Vulkan with --ozone-platform=wayland.
Upstream URL: https://www.google.com/chrome
Keywords: chromium
Licenses: custom:chrome
Conflicts: google-chrome
Provides: google-chrome
Submitter: prydom
Maintainer: prydom
Last Packager: prydom
Votes: 6
Popularity: 1.24
First Submitted: 2024-05-26 02:36 (UTC)
Last Updated: 2024-09-20 01:39 (UTC)

Dependencies (13)

Required by (41)

Sources (4)

Pinned Comments

prydom commented on 2024-09-20 01:41 (UTC)

I've bumped the package to its final version 128.0.6613.137. As suggested, I will flag the package outdated for now to let people know they should move to 129 post-haste.

prydom commented on 2024-08-08 17:44 (UTC)

This has landed upstream again at https://chromiumdash.appspot.com/commit/1d408de1538427653f776b5e5e646503d0d0f0c5 and is scheduled to be available in Chromium 129.

This AUR package tracks stable so this package will be retired in the second half of September 2024 if everything goes to plan.

prydom commented on 2024-05-26 02:38 (UTC)

This is a fork of https://aur.archlinux.org/packages/google-chrome which applies a one-byte binary patch to the proprietary Chrome build to enable Vulkan support when --ozone-platform=wayland is used. To use this patch add the following arguments to your chrome-flags.conf file:

--ozone-platform=wayland
--use-angle=vulkan

To enable VA-API support on AMD GPUs using the upstream Mesa drivers. First install Mesa 24.1 or later as https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/26165 must be merged for full support. Then add the following feature flags to your chrome-flags.conf (note that only one enable-features can be present in the file)

--enable-features=Vulkan,VulkanFromANGLE,DefaultANGLEVulkan,VaapiIgnoreDriverChecks,VaapiVideoDecoder,UseMultiPlaneFormatForHardwareVideo,VaapiVideoEncoder

The binary patch swaps gl::ANGLEImplementation::kOpenGLES with gl::ANGLEImplementation::kVulkan in WaylandSurfaceFactory::GetAllowedGLImplementations() which enables --use-angle=vulkan to be selected at the loss of using ANGLE's OpenGLES backend. Note that OpenGL and not OpenGLES is the default ANGLE backend and so there generally should be no loss of functionality due to this change. Both x11 and CPU fallbacks remain available.

More details can be found starting at page 41 of this forum thread https://bbs.archlinux.org/viewtopic.php?id=244031 and at the Chromium issue report https://issues.chromium.org/issues/334275637.

Latest Comments

1 2 Next › Last »

prydom commented on 2024-09-20 01:41 (UTC)

I've bumped the package to its final version 128.0.6613.137. As suggested, I will flag the package outdated for now to let people know they should move to 129 post-haste.

vjraitila commented on 2024-09-18 18:47 (UTC)

It seems the commit has landed in the latest Chrome stable and the binary patch is no longer required.

pqatsi commented on 2024-09-18 14:26 (UTC)

This AUR package tracks stable so this package will be retired in the second half of September 2024 if everything goes to plan.

I suggest just mark this package as outdated to keep history.

gothmog123 commented on 2024-09-01 07:00 (UTC)

@prydom thank you

prydom commented on 2024-08-31 15:58 (UTC)

@gothmog123, I don't use brave-bin and so I won't package it only to maintain it until next month when the code patch is available upstream.

However I can explain, the r2-binary-patch file that I provide here will work on Brave because both Chrome and Brave uses the Chromium vendored build toolchain. I actually use Brave's debug symbols to avoid building Chromium to develop this patch.

To manually patch Brave the command from this PKGBUILD that you want is r2 -q -N -i 'r2-binary-patch-script' -w brave. The Chromium major version (i.e. 128) must match between this package and Brave's version. You can verify the Chromium version at https://github.com/brave/brave-browser/releases. You can also edit the brave-bin PKGBUILD to include the r2 command as I have here.

gothmog123 commented on 2024-08-30 11:44 (UTC)

sorry could you do a brave-bin version with the amd vaapi patch as well?

or if not could you just exaplain how to patch that package?

prydom commented on 2024-08-08 17:44 (UTC)

This has landed upstream again at https://chromiumdash.appspot.com/commit/1d408de1538427653f776b5e5e646503d0d0f0c5 and is scheduled to be available in Chromium 129.

This AUR package tracks stable so this package will be retired in the second half of September 2024 if everything goes to plan.

prydom commented on 2024-07-24 18:11 (UTC)

As of 127.0.6533.72 (https://chromereleases.googleblog.com/2024/07/stable-channel-update-for-desktop_23.html) the binary signature used for the patch changed.

If you are applying the binary patch manually, please update your r2 script.

prydom commented on 2024-05-26 02:44 (UTC) (edited on 2024-05-26 03:00 (UTC) by prydom)

@yochananmarqos: I chose google-chrome-wayland-vulkan over google-chrome-wayland because Chromium does have Wayland support. This patch explicitly enables the Vulkan rendering backend when using Chromium's native Wayland support.

Additionally, with or without this patch, Vulkan works fine on Chromium's Ozone with X11 so renaming to google-chrome-vulkan does not seem right either.

prydom commented on 2024-05-26 02:38 (UTC)

This is a fork of https://aur.archlinux.org/packages/google-chrome which applies a one-byte binary patch to the proprietary Chrome build to enable Vulkan support when --ozone-platform=wayland is used. To use this patch add the following arguments to your chrome-flags.conf file:

--ozone-platform=wayland
--use-angle=vulkan

To enable VA-API support on AMD GPUs using the upstream Mesa drivers. First install Mesa 24.1 or later as https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/26165 must be merged for full support. Then add the following feature flags to your chrome-flags.conf (note that only one enable-features can be present in the file)

--enable-features=Vulkan,VulkanFromANGLE,DefaultANGLEVulkan,VaapiIgnoreDriverChecks,VaapiVideoDecoder,UseMultiPlaneFormatForHardwareVideo,VaapiVideoEncoder

The binary patch swaps gl::ANGLEImplementation::kOpenGLES with gl::ANGLEImplementation::kVulkan in WaylandSurfaceFactory::GetAllowedGLImplementations() which enables --use-angle=vulkan to be selected at the loss of using ANGLE's OpenGLES backend. Note that OpenGL and not OpenGLES is the default ANGLE backend and so there generally should be no loss of functionality due to this change. Both x11 and CPU fallbacks remain available.

More details can be found starting at page 41 of this forum thread https://bbs.archlinux.org/viewtopic.php?id=244031 and at the Chromium issue report https://issues.chromium.org/issues/334275637.

1 2 Next › Last »