On Edgy, I solved the problem by adding the -fp parameter to the /etc/vnc/config file as follows:
sudo gedit /etc/vnc/config
opens config file for r/w:
# Default vncserver configuration. See the vncserver man page for details.
-PasswordFile $HOME/.vnc/passwd # Location of VncAuth password
-desktop "$HOSTNAME:$DISPLAYNUM ($USER)" # Desktop name
-pn # Continue even if standard ports fail
-httpd <inline> # Serve Java viewer inline
#######################################
# Add correct X11 fonts path spec. Because vncserver does not
# recognize -fp, it passes it to Xvnc, which vncserver invokes (see man
# vncserver). Hence, this is equivalent to specifying
# Xvnc :1 -fp /usr/share...
On Edgy, I solved the problem by adding the -fp parameter to the /etc/vnc/config file as follows:
sudo gedit /etc/vnc/config
opens config file for r/w:
# Default vncserver configuration. See the vncserver man page for details.
-PasswordFile $HOME/.vnc/passwd # Location of VncAuth password $DISPLAYNUM ($USER)" # Desktop name
-desktop "$HOSTNAME:
-pn # Continue even if standard ports fail
-httpd <inline> # Serve Java viewer inline
####### ####### ####### ####### ####### ####
# Add correct X11 fonts path spec. Because vncserver does not
# recognize -fp, it passes it to Xvnc, which vncserver invokes (see man
# vncserver). Hence, this is equivalent to specifying
# Xvnc :1 -fp /usr/share...
-fp /usr/share/ fonts/X11/ Type1,/ usr/share/ fonts/X11/ 100dpi, /usr/share/ fonts/X11/ 75dpi,/ usr/share/ fonts/X11/ misc ####### ####### ####### ####### #####
#######