Mesa 18.3.6 has issues using EGL_PLATFORM_GBM_KHR and OpenGL Desktop Profile. Using the very same, we get an unsatisfied linkage error using desktop GL, see: * * java.lang.UnsatisfiedLinkError: 'int jogamp.opengl.gl4.GL4bcImpl.dispatch_glGetError1(long)' * at jogamp.opengl.gl4.GL4bcImpl.dispatch_glGetError1(Native Method) * at jogamp.opengl.gl4.GL4bcImpl.glGetError(GL4bcImpl.java:648) * at jogamp.opengl.GLContextImpl.setGLFunctionAvailability(GLContextImpl.java:2186) * at jogamp.opengl.GLContextImpl.createContextARBVersions(GLContextImpl.java:1427) * at jogamp.opengl.GLContextImpl.createContextARBMapVersionsAvailable(GLContextImpl.java:1366) * at jogamp.opengl.GLContextImpl.mapGLVersions(GLContextImpl.java:1223) * at jogamp.opengl.GLContextImpl.createContextARB(GLContextImpl.java:968) * at jogamp.opengl.egl.EGLContext.createImpl(EGLContext.java:318) * at jogamp.opengl.GLContextImpl.makeCurrentWithinLock(GLContextImpl.java:769) * at jogamp.opengl.GLContextImpl.makeCurrent(GLContextImpl.java:652) * at jogamp.opengl.GLContextImpl.makeCurrent(GLContextImpl.java:590) * at jogamp.opengl.egl.EGLDrawableFactory$SharedResourceImplementation.mapAvailableEGLESConfig(EGLDrawableFactory.java:858)
Type 'ANNOTATION' to document this issue being only referenced here, but caused by an external component -> Mesa.
We workaround this issue by simply not trying to probe the desktop profile in DRM_GBM mode and the EGLDrawableFactory.