As the title says, chromium-ozone-wayland will crash when trying to start it with --in-process-gpu (I cannot test it without this flag as my platform doesn't provide full blown kms/drm/dri/gbm/mesa drivers).
# Angle is not used by Wayland yet, but it was still built. It wasn't a problem
# until wayland-protocols were updated to 1.20 in newest yocto releases, which
# changed the implementation of the wayland-scanner tool. That tool uses a new
# API, which is not part of older wayland-protocols. And given ANGLE includes
# libwayland headers from //third_party/wayland instead of relaying on the
# system ones, that results in undeclared methods.
# TODO(msisov): remove this once Chromium's //third_party/wayland is updated
# to >=1.20. This tracks https://crbug.com/1359189
GN_ARGS += "\
angle_use_wayland=false \
"
I'm no expert on this, but the folks over at arch use this patch:
Hi there,
As the title says, chromium-ozone-wayland will crash when trying to start it with --in-process-gpu (I cannot test it without this flag as my platform doesn't provide full blown kms/drm/dri/gbm/mesa drivers).
With: https://github.com/OSSystems/meta-browser/commit/0f11e5ed0da3a622bbd7952400e7470815ded96a
I'm no expert on this, but the folks over at arch use this patch:
Using the above patch and removing:
angle_use_wayland=false
fixes the issue for me.