The other option is to use a virtual X framebuffer (Xvfb) and use that as DISPLAY 0:0
It does work, but it's not very stable > -----Original Message----- > From: Steve Brewin [mailto:[EMAIL PROTECTED] > Sent: 19 June 2003 09:29 > To: 'James Users List' > Subject: RE: Matchers & X Window > > > > Can't connect to X11 window server using ':0.0' > > as the value of the DISPLAY variable.java.lang.InternalError: Can't > > connect to X11 window server using ':0.0' as the value of > the DISPLAY > > variable. > > at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method) > > at > sun.awt.X11GraphicsEnvironment.<clinit>(X11GraphicsEnvironment > > .java:125) > > > Running on Solaris right? The Solaris implementation of AWT > requires a display device and by default uses DISPLAY 0:0. > According to Sun this is not a bug and will not be fixed. > > Look on Sun's site for various workarounds. > > Code wise, its best to steer well clear of AWT! > > -- Steve > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
