On 04/01/17 21:51, Attard, Mark I via shifter-users wrote: > Hi, > > Apologies if this email is misdirected, in which case can you point me in the > right direction please? This is the right place.
> I am having a new problem with xpra that I never had before: > > > xpra attach :7 > 2017-01-04 14:27:58,278 Xpra gtk2 client version 1.0 64-bit > 2017-01-04 14:27:58,381 running on Linux RedHatEnterpriseWorkstation 6.6 > Santiago > 2017-01-04 14:27:58,383 Warning: failed to import opencv: > 2017-01-04 14:27:58,383 No module named cv2 > 2017-01-04 14:27:58,384 webcam forwarding is disabled > 2017-01-04 14:27:59,469 GStreamer version 0.10.29 for Python 2.6.6 64-bit > > Gdk-ERROR **: 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 332 error_code 2 request_code 154 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.) > aborting... > Aborted (core dumped) Ouch. That's bad :( Strange thing is that I am not seeing this at all with CentOS 6.6, which should behave exactly the same as RHEL 6.6. > Any help will be greatly appreciated thanks. Please attach gdb to your client process and try to get a backtrace when it crashes. http://xpra.org/trac/wiki/Debugging#GDB It may also be helpful to include the last few lines of the client output when run with "-d all". Then there's also the usual suspects: try turning off opengl, clipboard, etc. Cheers Antoine > All the best for the New year, > Mark _______________________________________________ shifter-users mailing list [email protected] http://lists.devloop.org.uk/mailman/listinfo/shifter-users
