MFIX 21.4 see fault on VTK via ssh -XY and Xquartz 2.8.1/Mac; vtkOpenGLRenderWindow.c/vtkXOpenGLRenderWindow errors

Support
1

Using XQuartz 2.8.1 on macOs 12.3.1 Monterey, and setting defaults write org.xquartz.X11 enable_iglx -bool true MFIX crashes at the VTK loading part. Works fine on Windows, e.g., with Mobaxterm. We use RHEL 7 and X-forwarding, i.e., ssh -XY. Always a segfault when attempting to run it. See below debug/errors.

MESA_GL_VERSION_OVERRIDE=3.2 MESA_GLSL_VERSION_OVERRIDE=150 mfix -n -l info
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 /etc/drirc: No such file or directory.
libGL: Can't open configuration file /xyz/home/me/.drirc: No such file or directory.
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /xyz/home/me/.drirc: No such file or directory.
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
mfix - INFO - Welcome to MFiX - https://mfix.netl.doe.gov
mfix - INFO - MFiX-GUI version 21.4
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 /etc/drirc: No such file or directory.
libGL: Can't open configuration file /moto/home/rk3199/.drirc: No such file or directory.
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /moto/home/rk3199/.drirc: No such file or directory.
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast

2022-04-18 12:11:33.404 ( 55.046s) [ AAAEEEC0]vtkOpenGLRenderWindow.c:499 ERR| vtkXOpenGLRenderWindow (0x55555cf6a780): 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.

Segmentation fault

Is there any work around for this?

2

x-forwarding does not work well with OpenGL. You could use the first two solutions from the following post:

https://discourse.paraview.org/t/paraview-error-vgl/9440/2

3

Or, if you don’t need to display vis. on the screen - you are happy with just saving images, you can use something similar with the third solution - compile VTK to use a headless display.

4

Can you clarify what you mean by this? Saving images? We want the users to be able to use the VTK-driven 3D features. The -k (without VTK) option works just fine.

5

Sometimes you can produce visualization with fixed parameters instead of interactively exploring your data. In that case you can save that visualization image and examine it later.
This is commonly used for in situ visualization.

If you need interactivity your choices are turbovnc + virtualgl or nomachine.

Dan

6

Am I reading the docs correct that either TurboVNC or nomachine would need to be installed and running on the servers that provide the logsin/accounts?

7

Yes, that is correct.