Posted by Dolda2000 on Feb 06, 2014; 12:35pm
URL: https://forum.jogamp.org/Cannot-initialize-JOGL-on-Mesa-swrast-after-upgrade-tp4031458p4031479.html

>That would mean that the call to [glXChooseFBConfig] returns an array of PointerBuffer but one (1st and only one?) is a NULL ptr ?

No; as you can see from glxinfo, it returns 6 GLXFBConfigs, two of which are NULL.

> However, we could attempt a workaround, i.e. handle it upstream.

> Maybe you can test to catch the exception from glXGetFBConfig
> and return zero at FBCfgDrawableTypeBits ?

I find JOGL's build process a bit strange and weird, and must admit I am uninclined to try and understand it. :)

I did fix the bug in Mesa instead. It turns out that it maps XVisualInfos through a function that may return NULL for visuals that aren't usable for GL, so I simply made glXGetFBConfigs not include those NULL results in its list, and installed my fixed Mesa. The result is a list of usable GLXFBConfigs only, and that made JOGL continue properly. (I have also reported the bug to Debian now.)


However, having continued, it happened into a new problem:
javax.media.opengl.GLException: main-SharedResourceRunner: Error making temp context(1) current

I'm not sure if I should start a new thread for this, as it seems to be a separate problem. Either way, here's a new test_dbg.log which traces this problem: <http://www.dolda2000.com/~fredrik/tmp/test_dbg-2>