>
Thanks Alfonso - looks like I may have been wrong about VirtualGL working
correctly on my cluster. I had based this on vglrun working with firefox
and matlab, but after following your suggestions, I noticed that
VGL_DISPLAY was not set. I followed some troubleshooting steps on
virtualgl.org and found that glxgears wasn't opening and that firefox and
matlab were actually being rendered with software openGL. So the issue does
seem to be on my cluster, which makes more sense than standalone conn just
ceasing to work through VGL.

Thanks for your time!


> 1. conn17f (precompiled), conn18a (compiled)
>
2. xquartz with vglconnect
3. DISPLAY: gfx.brazos.tamu.edu:11.0; VGL_CLIENT: localhost;
VGL_DISPLAY: not set. VGL_DISPLAY not being set seemed odd, so I tried
setting it to :0.0 and tested with 'vglrun glxgears', and I got the same
error: [VGL] ERROR: Could not open display :0.0. This error occurred
without VGL_DISPLAY being set.
4. I had been able to open firefox and matlab with vglrun, but I just
noticed that when I open 'vglrun matlab' the command line says 'MATLAB is
selecting SOFTWARE OPENGL rendering.'. So it looks like the problem is with
VGL on my cluster, not with conn, and firefox and matlab hadn't been
running via OpenGL like I previously thought.