Hi Francesco, On Thu, 2021-02-18 at 13:47 +0100, Francesco P. Lovergine wrote: > On Thu, Feb 18, 2021 at 11:22:27AM +0100, Francesco P. Lovergine wrote: > > On Thu, Feb 18, 2021 at 10:56:04AM +0100, Francesco P. Lovergine wrote: > > > Update: I tested also with a vagrant installation of a testing64 vm > > > (from scratch), under a virtualbox provider. It gives exactly the > > > same result. IMHO 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. > > > > > > > ... 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. > > > > Ok, workaround: disable composite rendering, which could be done in both xfce > and mate settings, for instance. >
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 -- GPG Fingerprint 3DF5 E8AA 43FC 9FDF D086 F195 ADF5 0EDA F8AD D585
signature.asc
Description: This is a digitally signed message part
