Closed alkisg closed 2 years ago
This issue affects me too.
Attaching glxinfo.txt from an affected client.
It seems like marco is calling some Xorg function that other display managers do not call; then Xorg crashes. So it might not be a marco issue after all, but a Xorg or glamoregl issue. This one seems similar.
Workarounds so far:
Driver "intel"
in xorg.conf (for those using LTSP, it's X_DRIVER=intel
in ltsp.conf).xserver-command=env MESA_GL_VERSION_OVERRIDE=2.1 X
in lightdm.conf (for LTSP, it's LIGHTDM_CONF="xserver-command=env MESA_GL_VERSION_OVERRIDE=2.1 X"
).Attaching glxinfo.txt, lspci.txt and Xorg.log.txt from another affected client, after the xserver-command
workaround was applied.
Even though marco could be patched to avoid the problematic Xorg calls, this issue probably needs to be reported and fixed in glamor, not here. Closing.
Marco 1.26.0-3ubuntu1 in Ubuntu 22.04 with certain graphics cards and applications is causing Xorg crashes with the following message:
Replacing it with xfwm4 or with marco 1.24.0-1ubuntu2 resolves the issue. Running
marco --no-composite
does not help.I suspect that it affects all graphics cards/drivers that don't provide GLSL 1.30. One affected graphics card is:
One way to reproduce the issue is to run a VNC application fullscreen. I'm attaching the related Xorg.0.log.old, you can see the crash at its end.
Xorg.0.log.txt