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 Google Groups by Delali Dzirasa, 10 months ago
Can't connect to X11 window server using ':0.0' as the value of the DISPLAY variable.
via Google Groups by Delali Dzirasa, 10 months ago
Can't connect to X11 window server using ':0.0' as the value of the DISPLAY variable.
via Oracle Community by 807577, 2 years ago
Can't connect to X11 window server using ':0.0' as the value of the DISPLAY variable.
via Oracle Community by 807599, 1 year ago
Can't connect to X11 window server using ':0.0' as the value of the DISPLAY variable.
via Oracle Community by 791392, 1 year ago
Can't connect to X11 window server using ':0.0' as the value of the DISPLAY variable.
via justlinux.com by Unknown author, 2 years ago
Can't connect to X11 window server using ':0.0' as the value of the DISPLAY variable.
java.lang.InternalError: Can't connect to X11windowserver using ':0.0' as the value of the DISPLAY variable. at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method) at sun.awt.X11GraphicsEnvironment.<clinit>(X11GraphicsEnvironment.java:134) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:141) at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:62) at java.awt.Window.init(Window.java:231) at java.awt.Window.<init>(Window.java:275) at java.awt.Frame.<init>(Frame.java:401) at java.awt.Frame.<init>(Frame.java:366) at javax.swing.JFrame.<init>(JFrame.java:154) at apl.Frame1.<init>(Frame1.java:165) at apl.EngineeringDump.main(EngineeringDump.java:86)