Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Atlassian JIRA by James Dumay [Atlassian], 2 years ago
via Atlassian JIRA by James Dumay [Atlassian], 1 year ago
via Eclipse Bugzilla by veronika_irvine, 2 years ago
Can't start the AWT because Java was started on the first thread. Make sure StartOnFirstThread is not specified in your application's Info.plist or on the command line
via broadinstitute.org by Unknown author, 2 years ago
Can't connect to window server - not enough permissions.
via Stack Overflow by Blanka
, 2 years ago
Can't connect to window server - not enough permissions.
java.lang.InternalError: Could not start up the CDSA libraries.	at java.lang.ClassLoader$NativeLibrary.load(Native Method)	at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1878)	at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1779)	at java.lang.Runtime.loadLibrary0(Runtime.java:823)	at java.lang.System.loadLibrary(System.java:1045)	at com.apple.crypto.provider.HmacCore.(HmacCore.java:26)	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)	at java.lang.reflect.Constructor.newInstance(Constructor.java:513)	at java.lang.Class.newInstance0(Class.java:355)	at java.lang.Class.newInstance(Class.java:308)	at java.security.Provider$Service.newInstance(Provider.java:1221)