xpra_launcher -d all &> xpra.log
Does it happen if you connect using the command line instead of the launcher?
Can you post the output of xpra opengl-probe && echo $?
?
~/: xpra opengl-probe && echo $? The program 'Xpra' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 176 error_code 2 request_code 155 minor_code 3) (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 --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)
~/: xpra attach ssh://myhostalias The program 'Xpra' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 176 error_code 2 request_code 155 minor_code 3) (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 --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) 2019-04-22 19:46:12,221 Xpra GTK2 client version 2.5.1-r22431 64-bit 2019-04-22 19:46:12,222 running on Linux Ubuntu 18.04 bionic 2019-04-22 19:46:12,224 window manager is 'Xfwm4' 2019-04-22 19:46:15,213 GStreamer version 1.14.1 for Python 2.7.15 64-bit 2019-04-22 19:46:15,881 No OpenGL_accelerate module loaded: No module named OpenGL_accelerate The program 'xpra' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 212 error_code 2 request_code 155 minor_code 3) (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 --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)
Looks like your opengl drivers are buggy. Are you using an intel chipset?
Run the attach command with --opengl=no
and it should be fine.
xra attach -d opengl ssh://myalias &> xpra.attach.log
From IRC:
~/: xpra opengl-probe ; echo $?
returned 1.
2019-04-22 19:57:29,862 OpenGL probe command returned 1 for command=['python2', '/usr/bin/xpra', 'opengl-probe', '-d', 'opengl']
After that, we should NOT be trying to use the driver.
Please apply r22509 and see if that fixes things. If it does not, add this trivial patch:
--- xpra/client/gtk_base/gtk_client_base.py (revision 22509) +++ xpra/client/gtk_base/gtk_client_base.py (working copy) @@ -978,7 +978,7 @@ parts = enable_opengl.split(":", 1) enable_option = parts[0] #ie: "on" opengllog("init_opengl: enable_option=%s", enable_option) - if enable_option in ("probe-failed", "probe-error", "probe-crash"): + if enable_option in ("probe-failed", "probe-error", "probe-crash", "probe-warning"): msg = enable_option.replace("-", " ") if len(parts)>1: msg += ": %s" % csv(parts[1:])
Not heard back, so I assume that r22509 fixed things.
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/2281