Package Details: google-chrome-wayland-vulkan 126.0.6478.126-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: 4
Popularity: 1.93
First Submitted: 2024-05-26 02:36 (UTC)
Last Updated: 2024-06-25 17:58 (UTC)

Dependencies (13)

Required by (40)

Sources (4)

Pinned Comments

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

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.

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

Per @yochananmarqos' request I have migrated the package to https://aur.archlinux.org/packages/google-chrome-wayland-vulkan

yochananmarqos commented on 2024-05-26 00:13 (UTC)

@prydom: While the google-chrome package is a binary package, notice it does not have the -bin suffix as there is no source available as an alternative. Therefore, using it was not necessary to begin with let alone adding it in the wrong place. Hint: A suffix is just that. Please resubmit with a proper package name. I think just google-chrome-wayland would suffice.