From: Pawel Kedzierski (
Date: Tue Oct 10 2017 - 03:45:58 CDT

Dear all,

I have just tried the alpha version of VMD (1.9.4 alpha 8) and I
discovered that it crashes when run remotely. I guess the problem is
that the X11 connection (forwarded via ssh) switches the OpenGL renderer
to the software one. It is always the case, independently on the method
of connection - I tried "ssh -X" and X2Go Client from Ubuntu 16.04, and
also MobaXterm from Windows 10. The result is always this:

/usr/lib/x86_64-linux-gnu/ no version information available
(required by /usr/local/vmd1.9.4a8/vmd_LINUXAMD64)
Info) VMD for LINUXAMD64, version 1.9.4a8 (August 30, 2017)
Info) Email questions and bug reports to
Info) Please include this reference in published work using VMD:
Info)    Humphrey, W., Dalke, A. and Schulten, K., `VMD - Visual
Info)    Molecular Dynamics', J. Molec. Graphics 1996, 14.1, 33-38.
Info) -------------------------------------------------------------
Info) Multithreading available, 4 CPUs detected.
Info)   CPU features: SSE2 AVX AVX2 FMA
Info) Free system memory: 7448MB (94%)
Info) No CUDA accelerator devices available.
Warning) Detected X11 'Composite' extension: if incorrect display occurs
Warning) try disabling this X server option.  Most OpenGL drivers
Warning) disable stereoscopic display when 'Composite' is enabled.
Info) *OpenGL renderer: Gallium 0.4 on llvmpipe* (LLVM 3.5, 256 bits)
Info)   Full GLSL rendering mode is available.
Info)   Textures: 2-D (8192x8192), 3-D (512x512x512), Multitexture (8)
Segmentation fault

I know that the Gallium renderer crashes Pymol too, but VMD 1.9.2 used
to work (I haven't tried 1.9.3). So my questions are:

- it is expected not to work for this renderer? and if yes,

- does someone know a solution to make the forwarded X11 session use a
working OpenGL renderer?

Thanks in advance,