I just fixed it by changing Session type to XFCE instead of the default KDE in the Windows X2Go Client.
thank you for sharing your success
I can confirm that the experience on X2GO is noticeably faster and responsive compared to VNC. I am using Jetson Nano 2 gb wired into ethernet which also seems to help compared to using the WiFi adaptor.
You are welcome. I have run into another issue. Cheese works with VNC but with X2GO I am getting the error below.
vkapoor@vkapoor-desktop:~/Desktop$ cheese
libGL error: MESA-LOADER: failed to open swrast (search paths /usr/lib/aarch64-linux-gnu/dri:$${ORIGIN}/dri:/usr/lib/dri)
libGL error: failed to load driver: swrast
libGL error: MESA-LOADER: failed to open swrast (search paths /usr/lib/aarch64-linux-gnu/dri:$${ORIGIN}/dri:/usr/lib/dri)
libGL error: failed to load driver: swrast
(cheese:23889): Gdk-ERROR **: 06:47:57.261: The program ‘cheese’ received an X Window System error.
This probably reflects a bug in the program.
The error was ‘BadLength (poly request too large or internal Xlib length erro’.
(Details: serial 234 error_code 16 request_code 143 (GLX) minor_code 1)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Trace/breakpoint trap (core dumped)