XQuartz version and numpy?

[lee1043]

1. VCS not opening xwindow for Mac terminal when XQuartz 2.7.9 or higher version.
2. Loading variable returns error message which I've not seen before.

>>> import vcs, cdms2
>>> f=cdms2.open('clt.nc')
>>> d=f('clt')

/export_backup/lee1043/anaconda2/lib/python2.7/site-packages/numpy/ma/core.py:2761: DeprecationWarning: Non-string object detected for the array ordering. Please pass in 'C', 'F', 'A', or 'K' instead
order=order, subok=True, ndmin=ndmin)

>>> x=vcs.init()
>>> x.plot(d)

libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 149 (GLX)
Minor opcode of failed request: 3 (X_GLXCreateContext)
Value in failed request: 0x0
Serial number of failed request: 42
Current serial number in output stream: 43

[lee1043]

@doutriaux1 Do you have any idea about this issue?

[doutriaux1]

@lee1043 for now downgrade your XCode if possible. If not use a nox version of vcs on your remote system that will bypass this issue. I think that's the safer/faster way to go in general. @aashish24 @danlipsa is there anything that can be done on VTK side of things? I think it's related to the remote having very old version of drivers. @lee1043 let's ask tony to update our drivers.

[danlipsa]

@doutriaux1 @aashish24 There is nothing we can do in VTK. OpenGL does not work here, so VTK cannot work. This is the same direct rendering problem we have seen before. I suggest switching to vnc + vgl. I think it is going to be more reliable and faster than OpenGL X Forwarding. I paste here the results of me trying to connect to crunchy.

Charles,

On Wed, Sep 28, 2016 at 11:12 AM, Charles Doutriaux [email protected] wrote:
glxgears works fine in my "normal" configuration, but seg faults with the LIBGL env variable

I get the following error both on linux and mac when trying to connect to crunchy through x forwarding.

-bash-4.1$ LIBGL_DEBUG=verbose glxinfo
name of display: localhost:24.0
libGL: screen 0 does not appear to be DRI2 capable
libGL: OpenDriver: trying /usr/lib64/dri/tls/swrast_dri.so
libGL: OpenDriver: trying /usr/lib64/dri/swrast_dri.so
libGL: Can't open configuration file /export/lipsa/.drirc: No such file or directory.
libGL: Can't open configuration file /export/lipsa/.drirc: No such file or directory.
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 154 (GLX)
Minor opcode of failed request: 3 (X_GLXCreateContext)
Value in failed request: 0x0
Serial number of failed request: 27
Current serial number in output stream: 30

Which tells me that the driver tries to use direct rendering, but it does not find the required components on the client machine.
I wonder if your linux machine has the same mesa driver as crunchy, so this is why it works.

Indeed if I pass LIBGL_ALWAYS_INDIRECT=1 I get a similar error as you did:

-bash-4.1$ LIBGL_ALWAYS_INDIRECT=1 LIBGL_DEBUG=verbose glxinfo
name of display: localhost:24.0
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 154 (GLX)
Minor opcode of failed request: 3 (X_GLXCreateContext)
Value in failed request: 0x0
Serial number of failed request: 15
Current serial number in output stream: 18

This might be a driver issue: upgrading the driver/mesa might solve it.

Alternatively, vnc + vgl worked well for me.

[lee1043]

@doutriaux1 I've installed nox vcs and it works. Thanks!

[doutriaux1]

@scottwittenburg @danlipsa trying this today i get:

libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
ERROR: In ../Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx, line 761
vtkXOpenGLRenderWindow (0x55ec3e3c17e0): Unable to find a valid OpenGL 3.2 or later implementation. Please update your video card driver to the latest version. If you are using Mesa please make sure you have version 11.2 or later and make sure your driver in Mesa supports OpenGL 3.2 such as llvmpipe or openswr. If you are on windows and using Microsoft remote desktop note that it only supports OpenGL 3.2 with nvidia quadro cards. You can use other remoting software such as nomachine to avoid this issue.

I guess there's nothing to do about it right?