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
With the DRI_DRIVER_DIR issue out of the way, I see:
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.
render node is present:
$ ls -al /dev/dri/
total 0
drwxr-xr-x 3 root root
This could be a hint on why:
WARNING:ozone_platform_wayland.cc(273)] Failed to find drm render node path.
WARNING:wayland_buffer_manager_gpu.cc(424)] Failed to initialize drm render
node handle.
--
You received this bug notification because you are a member of Desktop
Packages, which is
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Bram Stolk (b-stolk)
** Changed in: chromium-browser (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in
The previous test was on a chromium 107 build.
I re-tested it on a chromium 110 build with minigbm, and it shows the same
result on rx580 gpu:
software compositing.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in
5 matches
Mail list logo
