Created attachment 35046 [details] glxinfo.txt I use Xquartz on an OSX box, remote ssh in to a Linux FC12 system. historically, it's been necessary to use LIBGL_ALWAYS_INDIRECT; this is the only config that gives sane glxinfo (see attached) On the remote linux system, mesa is 7.7-3: % rpm -qa|grep mesa mesa-libGL-devel-7.7-3.fc12.x86_64 mesa-libGLU-7.7-3.fc12.i686 mesa-libGLU-7.7-3.fc12.x86_64 mesa-libGLU-devel-7.7-3.fc12.x86_64 mesa-dri-drivers-7.7-3.fc12.x86_64 mesa-dri-drivers-7.7-3.fc12.i686 mesa-libGL-7.7-3.fc12.i686 mesa-libGL-7.7-3.fc12.x86_64 From the OSX box running Xquartz 2.5.0: % setenv LIBGL_ALWAYS_INDIRECT 1 % glxgears X Error of failed request: BadAlloc (insufficient resources for operation) Major opcode of failed request: 147 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Serial number of failed request: 22 Current serial number in output stream: 24 All remote openGL applications fail similarly - a window appears briefly, then dies. Apple's Jeremy Huddleston thinks it's a bug in remote mesa.
Works for me using my remote Gentoo box (Mesa-7.5 ... not a very recent test point)
related to #24226 ? ... maybe expecting a particular visual that XQuartz doesn't provide? ... but the error as BadAlloc seems odd...
Actually... I lied. On my remote Gentoo box, I have nVidia's libGL. That works fine using 'LIBGL_ALWAYS_INDIRECT=1 glxgears' ... but Mesa-7.5.2's libGL does show this failure.
Yeah... mesa is asking for an unsupported __GLXconfig We're seeing this logged: http://cgit.freedesktop.org/xorg/xserver/tree/hw/xquartz/GL/indirect.c?id=9ddbb03fa56aa73c3f417d8ee6433e45b94445b3#n555
http://cgit.freedesktop.org/~jeremyhu/xserver/commit/?id=5b0faf355465c9f21ad96e0ed266fbdbc29efb5b
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.