Posted by Sven Gothel on Aug 10, 2010; 8:09pm
URL: https://forum.jogamp.org/JOGL2-conflicting-with-GTK-tp1013991p1078049.html

We are about to evaluate this issue .. still.

initSingleton() is called within our code at 1st anyways (static initializer of GLProfile),
but there is currently no way to verify if another native or java call to the underlying
native windowing system has been made (which multithreading initialization is the issue here).

If anybody knows how to query if an X11 call has been already issued within a thread
[on a given display?] that would be great, since then we cannot initialize multithreading anymore
using XInitThreads() - too later. The latter was your issue here ..
If this is not possible (the current state) we will either opt-out or opt-in this behavior,
meaning that without XInitThreads we may have to block the whole X11[/AWT] usage for
every call - the prev. behavior.

The lack of using XInitThreads() is clearly a issue with the 'parent' application (here AWT),
and a work around is costly .. let's see.

~Sven