Created attachment 787 [details]
During my attempt to start application, I encountered a problem with jogl version 2.3.1. Logs are included in the attachement. Problem only occurs if I'm trying to start the application on account without admin rights. This user is not able to execute files like jogamp_exe_tst5971761952450585868.exe which are located in our temp folder. After creating new Executable Rule to this temp folder in Local Group Policy Editor everythings works fine, but I can't modify this on each client machine. Jogl version 2.1.2 worked properly (without executable rules added to system).
Could you check this ?
Disable the automated native library loading to work around this issue. This mechanism doesn't work in constrained environments, you'll have to use the Java library path, i.e "the old way".
Please provide the full logs with JOGL 2.3.2 instead of JOGL 2.3.1, not just a stack trace.
Katarzyna, welcome to the 'Software Restriction Policies (SRP)' club on Windows.
Be happy that the 'tool' didn't even froze the process,
we have a client with such case ;-)
Please try the current source version or next release,
if nothing helps - use "-Djogamp.gluegen.TestTempDirExec=false"
*** This bug has been marked as a duplicate of bug 1365 ***