string

(The numbers might be different but there should be only 1 file.) If other errors
result, re-install OpenGL, especially the SUNWglrt package.
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 the owner is not root, that is most likely the problem since there will be a
permission issue loading the graphic pipelines.
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
The Xservers file will be found in /usr/dt/config if you haven’t done any
customization but more likely /etc/dt/config/. Additional arguments after the
-nobanner option are acceptable.
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.
Alphabetical Message Listing 209