Technical article 127574

Some fonts are displayed as boxes when using tightvnc on OpenServer 5.0.7

OpenServer 5.0.7

Written · Last revised

Problem

After installing tightvnc from skunkware onto my 507 system, my remote desktop vnc connections are showing several boxes where text should be displayed, making the menu options unreadable.

NOTE:
      Tightvnc is an opensource VNC solution.  The 1.2.2 version
      has been compiled for OpenServer5 into a package available
      through skunkware.
The skunkware packages are not officially supported by SCO,
but are provided as a courtesy, in hopes that our customers
find them useful.

Solution

The easiest way to install tightvnc onto your 507, or 507v
system, is to use patchck.  For more information on
patchck see TA 126125 or
http://www.sco.com/support/patchck.html

If you have patchck installed, you can install selected skunkware packages using:

# patchck skunkware

Choosing tightvnc from the list, will also install the dependency packages glib and bash.

Alternatively, you can download and install these packages manually from the skunkware site:

ftp://ftp2.sco.com/pub/skunkware/osr5/vols/Glib-1.3-VOLS.tar
ftp://ftp2.sco.com/pub/skunkware/osr5/vols/bash-2.03-VOLS.tar
ftp://ftp2.sco.com/pub/skunkware/osr5/vols/tightvnc-1.2.2-VOLS.tar

Once tightvnc is installed, follow the steps below to complete the configuration.

If you do not already have an account which you wish to use with VNC, create a vnc user through scoadmin account manager.

Before using vnc as this user you must also assign a separate VNC password for this account using:

# su - vncuser -c /usr/local/bin/vncpasswd

This will setup a ~/.vnc/ directory in the user's $HOME.

You can modify the ~/.vnc/xstartup file to configure the
desktop displayed remotely.  For a regular user you might
have:
#!/bin/sh
PATH=$PATH:/usr/bin/X11:/usr/local/bin; export PATH
[ -f $HOME/.Xresources ] && xrdb $HOME/.Xresources
xsetroot -solid grey
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
pmwm &

If you are setting up VNC for remote administration as root, then you would probably want to display the normal SCOSession desktop using a /.vnc/xstartup file which looked like this:

#!/bin/sh
PATH=$PATH:/usr/bin/X11:/usr/local/bin; export PATH
[ -f $HOME/.Xresources ] && xrdb $HOME/.Xresources
scosession &
To avoid the font problem mentioned above, make some minor
changes to the vncserver script so that the vnc server
will use the local fonts on the server.  Backup and edit the file
/usr/local/bin/vncserver:
# cp /usr/local/bin/vncserver /usr/local/bin/vncserver.orig

Use your favorite editor and uncomment the following lines: (at approximately line #66)

&GetXDisplayDefaults();
(at approximately line #152)
$cmd .= " -fp unix/:7100";
$cmd .= " -fp /usr/lib/X11/fonts/misc/,/usr/lib/X11/fonts/75dpi/";
$cmd .= " -co /usr/lib/X11/rgb";

Start a vnc session for this user using:

# su - vncuser -c /usr/local/bin/vncserver vncuser

Then connect from your remote VNC client by pointing it to the desktop assigned as:

New 'X' desktop is hostname:1

Once you are finished with the remote connection, use this command to close it:

# /usr/local/bin/vncserver -kill :1
NOTE:
          For tightvnc on OpenServer 6 see TA 127227, which describes the VNC
          setup using tightvnc 1.3.9 on OSR6.  This describes configuring
          the xfs font server on OSR6 which also avoids this problem.

See also

TA 126125
http://www.sco.com/support/patchck.html
http://www.tightvnc.com/
http://www.sco.com/skunkware/
TA 127227
ACKNOWLEDGMENTS:

The solution to this problem was contributed by: David E. Nelson from United Laboratories, Inc.

From the Xinuos technical article database, record 127574. Reproduced with permission. The original is at www.sco.com/ta/127574, which is reachable but blocked from search engines.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.