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.
-- Francesco P. Lovergine
Attachment:
Schermata del 2021-02-18 11-16-50.png
Description: PNG image
