Hi! Thanks for testing it out!
I was wondering if it had to do with an user beeing logged in to lxde. I think autologin might be enabled on the jessie system. Unfortunately this does not help. Still the same problem on stretch. I have some additional info. Without exporting the inderect rendering flag it does not work on ssh either: > glxinfo|head libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast Error: couldn't find RGB GLX visual or fbconfig name of display: localhost:10.0 ... With the export still the same issue: >export LIBGL_ALWAYS_INDIRECT=1; glxinfo|head Error: couldn't find RGB GLX visual or fbconfig name of display: localhost:10.0 And there are no X error messages in the log either. I was wondering if it has to do something with the gl libs on the armhf build. Does your stretch based image have /usr/lib/*ARCH*/libGL.so.1.0.0 or /usr/lib/*ARCH*/libGL.so.1.2.0 installed? On jessie i havce 1.2.0, on stretch 1.0.0. The 1.2.0 seems to be in a "transitional package" that does not install anything useful?! Not sure if this is meaningful as glxinfo runs under lxde just fine. Adding iglx to the config on the BBB allows me to run glxinfo with DISPLAY=:0 (otehrwise I get X Error of failed request: GLXBadContext). But it did not change anything for running gl stuff on a remote screen. I also think the xserver on the BBB should not be necessary for running stuff via ssh -X on a remote screen. I think I killed the server on jessie once and ssh -X still worked fine. My ubuntu box is running with iglx. In addition running indirect GL stuff works for the jessie box on windows too. Again it does not work on stretch. Simon