Control: clone -1 -2 Control: reassign -1 marco Control: reassign -2 xfwm
Hi, On Do 18 Feb 2021 20:39:19 CET, Sven Geuer wrote:
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 xfceand 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
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 -- DAS-NETZWERKTEAM c\o Technik- und Ökologiezentrum Eckernförde Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde mobile: +49 (1520) 1976 148 landline: +49 (4351) 850 8940 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de
pgpCl7CTfK7Nf.pgp
Description: Digitale PGP-Signatur
