Broken HW accel for >vivaldi-7.7 under Wayland/Hyprland?

Dy · 2026-03-18 13:34:39

Hi,

I've noticed that newer builds of vivaldi break HW acceleration under Wayland/Hyprland - I have a laptop with two cards (Intel & Nvidia)

$ lspci  | rg -i VGA
00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-S UHD Graphics (rev 04)
01:00.0 VGA compatible controller: NVIDIA Corporation AD103GLM [RTX 5000 Ada Generation Laptop GPU] (rev a1)

When trying to play back (some) videos, I get a stream of errors like this & the whole UI of vivaldi breaks/freezes.

[170407:170407:0317/134305.383565:ERROR:chromium/ui/gl/angle_platform_impl.cc:42] ImageEGL.cpp:112 (operator()): eglCreateImage failed with 0x00003009
ERR: ImageEGL.cpp:112 (operator()): eglCreateImage failed with 0x00003009
[170407:170407:0317/134305.383770:ERROR:chromium/ui/gl/scoped_egl_image.cc:23] Failed to create EGLImage: EGL_SUCCESS
[170407:170407:0317/134305.383974:ERROR:chromium/ui/ozone/common/native_pixmap_egl_binding.cc:76] Unable to initialize binding from pixmap
[170407:170407:0317/134305.384091:ERROR:chromium/gpu/command_buffer/service/shared_image/ozone_image_backing.cc:316] OzoneImageBacking::ProduceSkiaGanesh failed to create GL representation
[170407:170407:0317/134305.384315:ERROR:chromium/gpu/command_buffer/service/shared_image/shared_image_manager.cc:404] SharedImageManager::ProduceSkia: Trying to produce a Skia representation from an incompatible backing: OzoneImageBacking
[170407:170407:0317/134305.400117:ERROR:chromium/ui/gl/angle_platform_impl.cc:42] ImageEGL.cpp:112 (operator()): eglCreateImage failed with 0x00003009
ERR: ImageEGL.cpp:112 (operator()): eglCreateImage failed with 0x00003009
[170407:170407:0317/134305.400370:ERROR:chromium/ui/gl/scoped_egl_image.cc:23] Failed to create EGLImage: EGL_SUCCESS
[170407:170407:0317/134305.400566:ERROR:chromium/ui/ozone/common/native_pixmap_egl_binding.cc:76] Unable to initialize binding from pixmap
[170407:170407:0317/134305.400641:ERROR:chromium/gpu/command_buffer/service/shared_image/ozone_image_backing.cc:316] OzoneImageBacking::ProduceSkiaGanesh failed to create GL representation
[170407:170407:0317/134305.400691:ERROR:chromium/gpu/command_buffer/service/shared_image/shared_image_manager.cc:404] SharedImageManager::ProduceSkia: Trying to produce a Skia representation from an incompatible backing: OzoneImageBacking
...

vivaldi://gpu:

Graphics Feature Status
=======================
*   Canvas: Hardware accelerated
*   Direct Rendering Display Compositor: Disabled
*   Compositing: Hardware accelerated
*   Multiple Raster Threads: Enabled
*   OpenGL: Enabled
*   Rasterization: Hardware accelerated on all pages
*   Raw Draw: Disabled
*   Skia Graphite: Disabled
*   TreesInViz: Disabled
*   Video Decode: Hardware accelerated
*   Video Encode: Software only. Hardware acceleration disabled
*   Vulkan: Disabled
*   WebGL: Hardware accelerated
*   WebGL2: Hardware accelerated
*   WebGPU: Disabled
*   WebNN: Disabled

Version Information
===================
Data exported              : 2026-03-18T13:31:26.348Z
Chrome version             : Chrome/7.7.3851.67
Operating system           : Linux 6.19.8-arch1-1
Software rendering list URL: https://chromium.googlesource.com/chromium/src/+/aea3c43f4f9b35bc42ef260397ea379e073d64ca/gpu/config/software_rendering_list.json
Driver bug list URL        : https://chromium.googlesource.com/chromium/src/+/aea3c43f4f9b35bc42ef260397ea379e073d64ca/gpu/config/gpu_driver_bug_list.json
ANGLE commit id            : 345a7754b882
2D graphics backend        : Skia/142 f4ed99d2443962782cf5f8b4dd27179f131e7cbe
Command Line               : /usr/sbin/vivaldi --user-data-dir=/home/user/.config/vivaldi_datadir --disk-cache-dir=/run/user/1000/chromium-cache --password-store=gnome-libsecret --force-dark-mode --enable-features=WebUIDarkMode --flag-switches-begin --enable-gpu-rasterization --disable-quic --show-autofill-signatures --ignore-gpu-blocklist --enable-smooth-scrolling --enable-features=WebUIDarkMode,ParallelDownloading,ReduceAcceptLanguage,WebRtcHideLocalIpsWithMdns,fill-on-account-select --flag-switches-end --ozone-platform=wayland --origin-trial-disabled-features=CanvasTextNg|WebAssemblyCustomDescriptors --render-node-override=/dev/dri/renderD129

Driver Information
==================
Initialization time             : 470
In-process GPU                  : false
Skia Backend                    : GaneshGL
Passthrough Command Decoder     : true
Sandboxed                       : false
GPU0                            : VENDOR= 0x10de, DEVICE=0x2730, DRIVER_VENDOR=Mesa, DRIVER_VERSION=26.0.2
GPU1                            : VENDOR= 0x8086, DEVICE=0xa788, DRIVER_VENDOR=Mesa, DRIVER_VERSION=26.0.2 *ACTIVE*
Optimus                         : true
AMD switchable                  : false
Pixel shader version            : 1.00
Vertex shader version           : 1.00
Max. MSAA samples               : 16

Did anyone encounter this issue as well? Could not figure out a solution through google so trying here

Last edited by Dy (2026-03-18 13:36:20)

5hridhyan · 2026-03-19 18:38:58

`--render-node-override=/dev/dri/renderD129` why?
first try with --disable-gpu-compositing

Edit:
if it works then, try with these:
--ozone-platform=wayland
--use-gl=egl
--ignore-gpu-blocklist
--disable-features=Vulkan,WaylandOverlayDelegation

Last edited by 5hridhyan (2026-03-19 19:08:03)

Dy · 2026-03-21 20:33:14

5hridhyan wrote:

`--render-node-override=/dev/dri/renderD129` why?

Tbh no idea, I don't have it in any configuration as far as I know...

--user-data-dir=/home/user/.config/vivaldi_datadir
#--disable-gpu-compositing
--ozone-platform=wayland
--use-gl=egl
--ignore-gpu-blocklist
--disable-features=Vulkan,WaylandOverlayDelegation
#--enable-features=UseOzonePlatform
#--ozone-platform=wayland
#--ozone-platform-hint=wayland
--disk-cache-dir=/run/user/1000/chromium-cache
--password-store=gnome-libsecret
--force-dark-mode
--enable-features=WebUIDarkMode

---

5hridhyan wrote:

first try with --disable-gpu-compositing
Edit:
if it works then, try with these:
--ozone-platform=wayland
--use-gl=egl
--ignore-gpu-blocklist
--disable-features=Vulkan,WaylandOverlayDelegation

Unfortunately neither of these helps fully - the UI now does not freeze, but the video is visibly choppy & laggy - seems like SW rendering/decoding is taking place which seems to be confirmed by the vivaldi://gpu:

Graphics Feature Status
=======================
*   Canvas: Software only. Hardware acceleration disabled
*   Direct Rendering Display Compositor: Disabled
*   Compositing: Software only. Hardware acceleration disabled
*   Multiple Raster Threads: Disabled
*   OpenGL: Disabled
*   Rasterization: Software only. Hardware acceleration disabled
*   Raw Draw: Disabled
*   Skia Graphite: Disabled
*   TreesInViz: Disabled
*   Video Decode: Software only. Hardware acceleration disabled
*   Video Encode: Software only. Hardware acceleration disabled
*   Vulkan: Disabled
*   WebGL: Disabled
*   WebGPU: Disabled
*   WebNN: Disabled

Without these supposedly get the HW acceleration, but a lot of eglCreateImage errors (and frozen UI when video is playing):

Graphics Feature Status
=======================
*   Canvas: Hardware accelerated
*   Direct Rendering Display Compositor: Disabled
*   Compositing: Hardware accelerated
*   Multiple Raster Threads: Enabled
*   OpenGL: Enabled
*   Rasterization: Hardware accelerated on all pages
*   Raw Draw: Disabled
*   Skia Graphite: Disabled
*   TreesInViz: Disabled
*   Video Decode: Hardware accelerated
*   Video Encode: Software only. Hardware acceleration disabled
*   Vulkan: Enabled
*   WebGL: Hardware accelerated
*   WebGPU: Hardware accelerated
*   WebNN: Disabled

seth · 2026-03-21 21:21:48

newer builds of vivaldi break HW acceleration under Wayland/Hyprland

Same for
* an X11 session
* a different wayland compositor (weston)
* --ozone-platform=x11
?

Dy · 2026-03-22 09:53:52

seth wrote:

newer builds of vivaldi break HW acceleration under Wayland/Hyprland
Same for
* an X11 session
* a different wayland compositor (weston)
* --ozone-platform=x11
?

Don't have X11 on this system, but sway behaves the same way.

Interestingly the platform=x11 *seems* to fix the issue although it is probably just a bandaid rather than a real fix, right? I have to figure out the HiDPI config for that one, window is huge

Graphics Feature Status
=======================
*   Canvas: Hardware accelerated
*   Direct Rendering Display Compositor: Disabled
*   Compositing: Hardware accelerated
*   Multiple Raster Threads: Enabled
*   OpenGL: Enabled
*   Rasterization: Hardware accelerated on all pages
*   Raw Draw: Disabled
*   Skia Graphite: Disabled
*   TreesInViz: Disabled
*   Video Decode: Hardware accelerated
*   Video Encode: Software only. Hardware acceleration disabled
*   Vulkan: Enabled
*   WebGL: Hardware accelerated
*   WebGPU: Hardware accelerated
*   WebGPU interop: Hardware accelerated
*   WebNN: Disabled

seth · 2026-03-22 23:25:32

Have you checked whether the older/unaffected Vivaldi versions defaulted to x11?
Can you disable the nvidia GPU in your UEFI settings?

Dy · 2026-03-22 23:27:53

seth wrote:

Have you checked whether the older/unaffected Vivaldi versions defaulted to x11?

I don't think it did, because when it uses X11, its HiDPI settings is wrong (double the size of UI) so I'd notice.

seth wrote:

Can you disable the nvidia GPU in your UEFI settings?

Nope, unfortunately not. But I probably could unload/blacklist nvidia modules though?

seth · 2026-03-22 23:34:31

You might want to check back on that - also whether this is actually > vivaldi 7.7 or "around the time when vivaldi 7.7 was randomly updated"

GPU0                            : VENDOR= 0x10de, DEVICE=0x2730, DRIVER_VENDOR=Mesa, DRIVER_VERSION=26.0.2
GPU1                            : VENDOR= 0x8086, DEVICE=0xa788, DRIVER_VENDOR=Mesa, DRIVER_VERSION=26.0.2 *ACTIVE*

doesn't even suggest you're using nvidia…

Try "pci_stub.ids=10de:2730", https://wiki.archlinux.org/title/Kernel_parameters

Dy · 2026-03-23 00:06:15

seth wrote:

You might want to check back on that - also whether this is actually > vivaldi 7.7 or "around the time when vivaldi 7.7 was randomly updated"

Around that time - I unfortunately don't really remember, I had to deal with some other issues so I kept rolling Vivaldi back hoping the issue will go away. Alas, that did not happen

seth wrote:

doesn't even suggest you're using nvidia… Try "pci_stub.ids=10de:2730", https://wiki.archlinux.org/title/Kernel_parameters

Explicitely not (atleast for Vivaldi) - the internal GPU should be plenty good enough to decode 2k stream from YT though (if I'm not terribly mistaken?). If I remember correctly, I *can* disable the Intel GPU and go only with nvidia, but that literally halves the battery life. TBH I'd rather use Vivaldi in xorg mode than going nvidia-only

The pci_stub.ids would prevent anything using nvidia, right? I remember using something like that when I was trying to pass GPU to QEMU VM... I can't really run this option full time because it kills the HDMI output I need. But I can certainly try & report back.

seth · 2026-03-23 16:00:36

so I kept rolling Vivaldi back hoping the issue will go away

That however means it's the Vivaldi version and didn't just start to happen around the time (for unrelated updates)

The pci_stub.ids would prevent anything using nvidia, right?

Yup.

it kills the HDMI output I need

Every approach to deprive the GPU of any driver would, but

But I can certainly try & report back.

That would be the plan - to see whether vivaldi (or your wider config) trips over the mutli-gpu setup and tries to use the GPU and IGP at the same time.

Arch Linux

#1 2026-03-18 13:34:39

Broken HW accel for >vivaldi-7.7 under Wayland/Hyprland?

#2 2026-03-19 18:38:58

Re: Broken HW accel for >vivaldi-7.7 under Wayland/Hyprland?

#3 2026-03-21 20:33:14

Re: Broken HW accel for >vivaldi-7.7 under Wayland/Hyprland?

#4 2026-03-21 21:21:48

Re: Broken HW accel for >vivaldi-7.7 under Wayland/Hyprland?

#5 2026-03-22 09:53:52

Re: Broken HW accel for >vivaldi-7.7 under Wayland/Hyprland?

#6 2026-03-22 23:25:32

Re: Broken HW accel for >vivaldi-7.7 under Wayland/Hyprland?

#7 2026-03-22 23:27:53

Re: Broken HW accel for >vivaldi-7.7 under Wayland/Hyprland?

#8 2026-03-22 23:34:31

Re: Broken HW accel for >vivaldi-7.7 under Wayland/Hyprland?

#9 2026-03-23 00:06:15

Re: Broken HW accel for >vivaldi-7.7 under Wayland/Hyprland?

#10 2026-03-23 16:00:36

Re: Broken HW accel for >vivaldi-7.7 under Wayland/Hyprland?

Board footer