"X"

X connection to string:0.0 broken (explicit kill or server shutdown).

Cause

This means that the client has lost its connection to the X server. The "0.0" represents the display device, which is usually the console. This message can appear when a user is running an X application on a remote system with the DISPLAY set back to the original system and the remote system's X server disappears, perhaps because someone exited X windows or rebooted the machine. It sometimes appears locally when a user exits the window system. Data loss is possible if applications were killed before saving files.

Action

Try to run the application again in a few minutes after the system has rebooted and the window system is running.

xinit: not found

Cause

OpenWindows was probably not installed properly, and the openwin(1) program could not find xinit(1) to start the X windows system. If the user is running another version of X windows, such as the MIT X11 distribution, the startx program serves the same function as xinit(1).

Action

Check the PATH environment variable to make sure it contains the appropriate X windows install directory. Verify that xinit(1) is in this directory as an executable program.

XIO: fatal IO error 32 (Broken pipe) on X server "string:0.0"

Cause

This means that I/O with the X server has been broken. The "0.0" represents the display device, which is usually the console. This message can appear when a user is running Display PostScript applications and the X server disappears or the client is shut down. Data loss is possible if applications disappeared before saving files.

Action

Try to run the application again in a few minutes after the system has rebooted and the window system is running.

Xlib: connection to "string:0.0" refused by server

Cause

This message is immediately followed by the "Xlib: Client is not authorized to connect to Server" message. These messages indicate that an X windows application tried to run on the X server specified inside double quotes, which did not allow the request. The "0.0" represents the display device, which is usually the console. If no server name appears, the superuser probably tried to run an X application on the current machine in an X session that was owned by somebody else.

Action

To allow this client to connect to the X server, run xhost(1) +clientname on the X server system. Only the owner of the current X session (who is not necessarily the superuser) is allowed to run the xhost(1) command. If somebody else is running X windows on the server, ask them to log out and then start your own X session on that server; remote X connections are usually allowed for the same user ID.

Xlib: extension "GLX" missing on display "0.0"

Cause

Install OpenGL 1.0 and test the configuration by running /usr/openwin/demo/GL/ogl_install_check which results in following:

# ./ogl_install_check
    Xlib:  extension "GLX" missing on display "0.0".
    Xlib:  extension "GLX" missing on display "0.0".
    Xlib:  extension "GLX" missing on display "0.0".
    can't find visual

Action

First check that the installation has worked correctly by running the package check utility on the runtime package: # pkgchk SUNWglrt. This should result in an error message such as:

	ERROR: /usr/openwin/server/etc/OWconfig
	    file size <187> expected <5423> actual
	    file cksum <14394> expected <27045> actual

Assuming that is fine, look at the process owner for the Xsun process using:

 
# ps -aef | grep Xsun | grep -v grep
nobody 20022   225  0 11:36:22 ?        0:34 /usr/openwin/bin/Xsun :0 -nobanner 

If you are are using CDE, ensure that the Xservers file has the form

:0 Local local_uid@console root /usr/openwin/bin/Xsun :0 -nobanner 

Another way of proving this is to run OpenWindows from the command line as root. It will ensure that the Xsun process is owned by root.

Another possibility is that the system is NOT a Creator 3D. You can only run openGL 1.0 on an Ultra with a Creator 3D graphics card. If you install this application on an Ultra with a Creator framebuffer and NOT a Creator 3D you'll see these same error messages.

xterm: fatal IO error 32 (Broken Pipe) or KillClient on X server "string:0.0"

Cause

This means that xterm(1) has lost its connection to the X server. The "0.0" represents the display device, which is usually the console. This message can appear when a user is running xterm and the X server disappears or the client gets shut down. Data loss is possible if applications were killed before saving files.

Action

Try to run the terminal emulator again in a few minutes after the system has rebooted and the window system is running.

XView warning: Cannot load font set 'string' (Font Package)

Cause

This message from the XView library warns that a requested font is not installed on the X server. Often multiple warnings are displayed for the same font. The set of available fonts can vary from release to release.

Action

To see which fonts are available on the X server, run the xlsfonts(1) program. Then specify another font name that you see in the output of xlsfonts(1). Sometimes it is possible to locate a similar font from a different vendor.

Technical Notes

There are two packages of X windows fonts: the common but not required fonts (SUNWxwcft), and the optional fonts (SUNWxwoft). Run pkginfo(1) to see if both packages are installed, and add them to the system as you want.