[Previous]   [Next]   [Contents]   [Index]

Solving Client Startup Problems

The following are common problems encountered with X clients:

Reliance on R3 Bugs

Some old clients may rely on X11R3 bugs for some features. For example, some X11R4 versions of xterm (but not the local client shipped with ENWARE) use an X11R3 bug for displaying popup menus. If you find that a client runs with an X11R3 server, but does not run with the current X server, try switching on [R3 Compatible].

Some clients do not rely on the user to set the font path and attempt an X_SetFontPath to find the fonts they need. With versions later than X11R3, if this attempt fails, the server returns an error and the client hangs even if the required font is already in the font path. The client may begin to work if you go to the configuration screens and switch on [R3 Compatible]. Another fix is to move the required fonts to the directory where the application expects to find them.

Missing Fonts

A client may also hang or quit if it requests fonts that are not in the font search path of the X server. To determine the font path, look on the [Server] configuration screen. You can change the font path by typing in new paths.

DISPLAY Variable Not Set

If you log into a computer using TELNET, you must set the DISPLAY variable to the X station's ip_address:0.0 (use DISPLAY=ip_address:0.0 ; export DISPLAY for Korn or Bourne shell setenv DISPLAY ip_address:0.0 for C shell.)

Insufficient Memory

If low-memory warnings pop up on your screen, you need more memory.

If backing store is on, you should be able to free up some memory by going to the configuration screens and switching it off. Press and hold [F12] to access the configuration screens. If the Backing Store button reads [When Mapped] or [By Application], click on it until it reads [Disabled]. Click on [OK] and then reboot your X station.

If you are using local clients, you may need to stop and use host-based versions instead. For more information about local clients and memory requirements, refer to Using X Station Memory Effectively.

You can also add more memory to your X station.

Too Many Clients

The X station supports in excess of 100 clients at the same time.

Too Many Connection Requests

The X station queues up to 25 requests from the computer to open connections to the X server at the same time. If you attempt to open more than 25 clients too quickly, some may fail to open.

Local Client Not Found

If the login server and the boot server are different, do the following:

  1. Copy the hpxt binaries from the login server to the boot server. The path (on both servers) is:
    /usr/bin/X11/700X/hpxt.*
    or, for HP-UX 10.x:
    /opt/hpxt/enware/bin/hpxt.*

  2. If the login server is running HP-UX 10.x, create the following link:
    ln -s /opt/hpxt/enware/bin /usr/bin/X11/700X 
[Previous]   [Next]   [Contents]   [Index]