Various issues with running labwc within a VM since moving to wlroots 0.17

[Consolatis]

This is a collection if issues that were raised since we moved to wlroots 0.17:

• labwc 0.7.0 fails to run wezterm, gitk on a vmware vm #1361
• leafpad crashing under labwc 0.7.0 (segfault?) #1445
• Error While Launching Some Applications: importing the supplied dmabufs failed #1732
• vmware: gvim let labwc compositor crash #1793
• https://bugs.debian.org/1071441 (sway crash report)
• https://gitlab.freedesktop.org/wlroots/wlroots/-/issues/3788

Lets use this issue for tracking and close the other ones to keep the information in a single place.

[tranzystorekk]

Tip for anyone passing by: some of these issues can be worked around by more aggresively forcing software rendering e.g. with LIBGL_ALWAYS_SOFTWARE=1

[knm100]

Some gtk programs (e.g. helvum) failed to start and Output a GDKmessage.
Gdk-Message: 12:39:18.614:Error 71 (Protocol error) dispatching to Wayland display
Is it also because of this?

[johanmalm]

Some gtk programs (e.g. helvum) failed to start and Output a GDKmessage. Gdk-Message: 12:39:18.614:Error 71 (Protocol error) dispatching to Wayland display Is it also because of this?

Hard to say. Were you running in VM when you got the message? Have you tried running with LIBGL_ALWAYS_SOFTWARE=1?

[knm100]

Helvum can start with LIBGL_ALWAYS_SOFTWARE=1 in VM

Were you running in VM when you got the message?

yes.