xfwm4 crash when using x2go

[Chris Green]

I just noticed that xfwm4 crashes when I run an x2go session, it
didn't used to do this, it *may* have started when I upgraded to
xubuntu 20.10.

When it crashed I started a new xfwm4 from a terminal, this provides
the following crash report when it too crashes (again when running
x2go):-

    xfwm4:15183): Gdk-ERROR **: 11:27:33.867: The program 'xfwm4' received
    an X Window System error.
    This probably reflects a bug in the program.
    The error was 'XSyncBadAlarm'.
      (Details: serial 213260 error_code 135 request_code 134 (SYNC) minor_code 11)
      (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)

Is this a bug in xfwm4 or in x2go?


-- 
Chris Green
·