Confirmed that this still affects Ubuntu 10.04 Server, forwarding onto a Mac OS X 10.6 system. However the
% setenv LIBGL_ALWAYS_INDIRECT yes
work around before running the affected application seems to resolve the problem.
Whereas direct rendering means that application can access the GPU hardware directly without communication with the X server first via Mesa, indirect rendering means that the GLX protocol will be used to transmit OpenGL commands and the X server will do the real drawing. Direct rendering is faster as it does not require change of context into X process of course, although in both cases rendering is done on the GPU if acceleration is present.
Confirmed that this still affects Ubuntu 10.04 Server, forwarding onto a Mac OS X 10.6 system. However the
% setenv LIBGL_ALWAYS_ INDIRECT yes
work around before running the affected application seems to resolve the problem.
Whereas direct rendering means that application can access the GPU hardware directly without communication with the X server first via Mesa, indirect rendering means that the GLX protocol will be used to transmit OpenGL commands and the X server will do the real drawing. Direct rendering is faster as it does not require change of context into X process of course, although in both cases rendering is done on the GPU if acceleration is present.