#983139 Artifacts in x2go rendering connecting to testing from a buster client

Package:
xfwm4
Source:
xfwm4
Description:
window manager of the Xfce project
Submitter:
"Francesco P. Lovergine"
Date:
2021-02-20 10:33:02 UTC
Severity:
important
#983139#5
Date:
2021-02-15 19:28:20 UTC
From:
To:
See for instance the included screenshot for xfce4. It is better for mate but
still there are black borders around application windows. Apparently it is
an issue with x2go-server, not sure if it depends on the host platform.
#983139#10
Date:
2021-02-18 09:56:04 UTC
From:
To:
this bug should be raised to important or grave because could render unusable
the x2goserver in bullseye for many (if not most) use cases :-( I still did
not check the use of bullseye from a bullseye client or other platforms.
#983139#15
Date:
2021-02-18 10:22:27 UTC
From:
To:
... and it gives the same artifacts using a bullseye client (which works
perfectly while connecting a buster x2go server). So this is definitively an
issue of the x2goserver in bullseye.
#983139#20
Date:
2021-02-18 12:47:07 UTC
From:
To:
and mate settings, for instance.
#983139#25
Date:
2021-02-18 19:39:19 UTC
From:
To:
Hi Francesco,

Looks like xfce4 and mate started to make use of the composite X
extension. This extension is not supported by the NX libs used with
x2go as documented on the project's home page [1].

For mate and tightvncserver on bullseye I observed the identical issue
a few days ago, and tightvncserver also lacks the composite extension.

Seems as if you have to live with the workaround.

Sven

[1] https://wiki.x2go.org/doku.php/wiki:development:roadmap#first_attempt_at_documenting_missing_nx-libs_features_for_certain_applications_and_desktop_environments
#983139#30
Date:
2021-02-19 22:40:47 UTC
From:
To:
Hi,

This issue actually is to be amended in xfwm and marco (and possibly
other window managers).

Those window manager need to test, whether the Composite extension is
available in the Xserver being used or not.

Mike