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.

--
Francesco P. Lovergine

Reply via email to