Chromium GPU Process Cannot Start

NVIDIA Open GPU Kernel Modules Version

555.42.02

Please confirm this issue does not happen with the proprietary driver (of the same version). This issue tracker is only for bugs specific to the open kernel driver.

• I confirm that this does not happen with the proprietary driver package.

Operating System and Version

Arch Linux

Kernel Release

Linux 6.9.1-hardened1-1-hardened #1 SMP PREEMPT_DYNAMIC Mon, 20 May 2024 12:54:08 +0000 x86_64 GNU/Linux

Please confirm you are running a stable release kernel (e.g. not a -rc). We do not accept bug reports for unreleased kernels.

• I am running on a stable kernel release.

Hardware: GPU

GPU 0: NVIDIA GeForce RTX 4060 Laptop GPU (UUID: GPU-57e1b957-4845-a325-50fb-12cb069295cd)

Describe the bug

When starting Chromium (or any chromium based program) using the --ozone-platform=wayland flag, the GPU process for Chromium cannot start, thus causing hardware acceleration to be completely unavailable- even if the browser is not tasked with performing the hardware acceleration on the Nvidia GPU.

Relevant parts of the Chromium event log:

[1182:1182:0521/234950.186727:ERROR:gl_display.cc(520)] : EGL Driver message (Critical) : eglCreateImage failed with 0x00003003
[1182:1182:0521/234950.186814:ERROR:scoped_egl_image.cc(23)] : Failed to create EGLImage: EGL_BAD_ALLOC
[1182:1182:0521/234950.187022:ERROR:native_pixmap_egl_binding.cc(113)] : Unable to initialize binding from pixmap
[1182:1182:0521/234950.187082:ERROR:ozone_image_backing.cc(365)] : OzoneImageBacking::ProduceSkiaGanesh failed to create GL representation
[1182:1182:0521/234950.187126:ERROR:shared_image_manager.cc(232)] : SharedImageManager::ProduceSkia: Trying to produce a Skia representation from an incompatible backing: OzoneImageBacking
GpuProcessHost: The GPU process exited with code 8704.

To Reproduce

• Launch chromium (or equivalent) with --ozone-platform=wayland flag, so that chromium is running as a native wayland app (and not via Xwayland)

Note: hardware acceleration is active and performs correctly when Chromium is running via XWayland

Bug Incidence

Always

nvidia-bug-report.log.gz

nvidia-bug-report.log.gz

More Info

No response

Start by reviewing the attached nvidia-bug-report.log.gz and reproducing the Chromium launch with --ozone-platform=wayland on the reported Arch Linux kernel and GPU. Compare the native Wayland failure with the working XWayland case; done means the Chromium GPU process starts and hardware acceleration works under native Wayland.