mesa builds, but "Failed to initialize GLX"

[gregfi]

I have built VisIt 3.2.2 on SuSE 12 SP5 using GCC 8.3.0 with the following command:

../build_visit3_2_2 --silo --silex --xdmf --szip --netcdf --hdf4 --hdf5 --cgns --boxlib --adios2 --mesagl --llvm --makeflags -j16 --version 3.2.2

The build succeeds, but when I try to launch VisIt on a machine without GL support, I get:

Running: gui3.2.2 Qt: Warning: QXcbConnection: Failed to initialize GLX

Can someone take a look at my build log and guess at the issue?

build_visit3_2_2_log.txt.gz

Also, side note of a couple minor issues:

• to get the build_visit script to work, I needed to add hyphens to Line 800 and 1269 because it was trying to find visit3.2.2.tar.gz instead of visit-3.2.2.tar.gz.
• this is an offline build, and I needed to manually download FMS-0.2.tar.gz and nektar-5.0.0.tar.gz, which are not in the official listing of third party libraries here: https://github.com/visit-dav/third-party/releases
• It would be very helpful for offline builders if the third-party libraries could be bundled into a single download.

[biagas]

Did you use VisIt to build Qt? Before or after you added --mesagl?
You may want to take a look at the X11 Qt dependencies that may need to be installed on your system.

For problems downloading thirdparty i/o packages like fms, add '--no-thirdparty'. Then you will only get the i/o libraries you specifically request.

[gregfi]

Yes, VisIt is building Qt, and it's happening after Mesa. (Does the order of the command line arguments matter?)

The only thing in the Qt configure output that seems like it might be missing is:

Checking for xkbcommon-x11... no

I can ask my admins to install that and try again. However, the overall Qt configure output is below. It seems like everything is enabled.

OpenGL:
Desktop OpenGL ....................... yes
...
xkbcommon .............................. yes
X11 specific:
XLib ................................. yes
XCB Xlib ............................. yes
EGL on X11 ........................... yes

[gregfi]

After some additional investigation with our admins, this issue seems related to our specific setup.