-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
x.plot crashes with OpenGL2 error (X server in XDMCP mode) #393
Comments
Now, from the same VcXsrv+XDMCP, if I ssh to a remote server where I have also installed CDAT 8.1, I get a slightly different error glxinfo gives me the following output
And when I run the same vcs test as above, I end up with a LOT of error output (I have just pasted part of the end below, anyway I can't scroll to the beginning, there is too much output), and a blank/empty canvas. I'm back at the python prompt, no crash like the previous test
x.png generates another load of errors and I'm back at the prompt x.interact() generates other errors, below (especially when I move the cursor over the canvas), but "q" gets me back to the prompt
The following mesa libs are installed on this server
|
@scottwittenburg @danlipsa looks like yet another case of older X server. @jypeter I think the switch to OenGL2 essentially made it incompatible with older X server... I think you will have to use the mesalib version here and ask users to first dump to a png. Other options are to upgrade your X server. Is that correct @danlipsa @scottwittenburg |
I have tried in a remote notebook (on the remote server mentioned just above), and it's not working either, but I have to go
|
The Mesa library seems new enough but for some reason it does not provide OpenGL 3.2 which is needed for this version of VTK. One path to address this kind of problems in the future is to ship our own mesalib even with the on-screen version of vcs and use an option to switch between using the system driver (which in this case does not work) and using the mesa OpenGL that we ship with our software. ParaView already does this. See options at the end of the following blog: https://blog.kitware.com/messing-with-mesa-for-paraview-5-0vtk-7-0/ |
@doutriaux1 Indeed for now the workaround is to use the offscreen version of vcs. |
@doutriaux1 First test of vcs in 8.1 and I get a crash
My setup
Windows 7 machine, running VcXsrv X server in XDMCP mode
I have unselected "Native opengl" because otherwise my X server crashes if I try to execute "glxgears" (event with LIBGL_ALWAYS_INDIRECT=1)
glxinfo
in a terminal on my server (when running VcXsrv+XDMCP) gives me the following outputMy test
Now, I get the following when trying my simple vcs test
I have the following rpm installed on the server
The text was updated successfully, but these errors were encountered: