I have reproduced this with a chromium that I built manually, from source, not going via snapcraft. So that rules out snap as the culprit, I think.
reproduced with: 112.0.5572.0 Built with: use_system_minigbm = false use_intel_minigbm = true use_amdgpu_minigbm = true WARNING:ozone_platform_wayland.cc(273)] Failed to find drm render node path. WARNING:wayland_buffer_manager_gpu.cc(437)] Failed to initialize drm render node handle. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2006646 Title: hwacc branch builds with minigbm switch to software compositor on amd. Status in chromium-browser package in Ubuntu: In Progress Bug description: This pertains to the hwacc branches of snap_from_source chromium builds. Following the guide-0.9.1, we switched from system gbm to minigbm. (These switches are in args.gn) use_system_minigbm = false use_intel_minigbm = true use_amdgpu_minigbm = true This enables us to better support intel hardware. However, there seems to be a regression on other gpus. Chromium will switch to software compositing on amd. When I revert back to system gbm, I get hardware compositing again. See attached screenshot. To reproduce: build chromium in two different ways, and compare the output from the chrome://gpu url. tested on: Radeon RX580 GPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006646/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
