I tend to blame xfwm4. The error message also points to that direction... When does this happen? Before starting a session? While starting a session? During a session?
Uli On Mon, Jan 18, 2021 at 10:59 AM Chris Green <c...@isbd.net> wrote: > > I've recently upgraded my system to xubuntu 20.10 and x2go sessions > now crash the xfwm4 window manager. After restarting xfwm4 from a > terminal window I see the following crash report when I run another > x2go session:- > > 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 > _______________________________________________ > x2go-user mailing list > x2go-user@lists.x2go.org > https://lists.x2go.org/listinfo/x2go-user _______________________________________________ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
