LinuxQuestions.org - problem with vnc

- Ubuntu (https://www.linuxquestions.org/questions/ubuntu-63/)

- - problem with vnc (https://www.linuxquestions.org/questions/ubuntu-63/problem-with-vnc-385566/)

problem with vnc

i'm trying to get vnc working on my pc. i got everything installed just fine, but when i try to execute vncserver i get this error:

Code:

jnev@jnevubuntu:~$ vncserver

Found /usr/share/tightvnc-java for http connections.

Couldn't start Xtightvnc; trying default font path.

Please set correct fontPath in the vncserver script.

Couldn't start Xtightvnc process.



22/11/05 12:33:49 Xvnc version 3.3.tight1.2.9

22/11/05 12:33:49 Copyright (C) 1999 AT&T Laboratories Cambridge.

22/11/05 12:33:49 Copyright (C) 2000-2002 Constantin Kaplinsky.

22/11/05 12:33:49 All Rights Reserved.

22/11/05 12:33:49 See http://www.uk.research.att.com/vnc for information on VNC

22/11/05 12:33:49 See http://www.tightvnc.com for TightVNC-specific information

22/11/05 12:33:49 Desktop name 'X' (jnevubuntu:1)

22/11/05 12:33:49 Protocol version supported 3.3

22/11/05 12:33:49 Listening for VNC connections on TCP port 5901

22/11/05 12:33:49 Listening for HTTP connections on TCP port 5801

22/11/05 12:33:49  URL http://jnevubuntu:5801

Font directory '/usr/X11R6/lib/X11/fonts/Type1/' not found - ignoring

Font directory '/usr/X11R6/lib/X11/fonts/Speedo/' not found - ignoring

Font directory '/usr/X11R6/lib/X11/fonts/misc/' not found - ignoring

Font directory '/usr/X11R6/lib/X11/fonts/75dpi/' not found - ignoring

Font directory '/usr/X11R6/lib/X11/fonts/100dpi/' not found - ignoring



Fatal server error:

could not open default font 'fixed'

22/11/05 12:33:50 Xvnc version 3.3.tight1.2.9

22/11/05 12:33:50 Copyright (C) 1999 AT&T Laboratories Cambridge.

22/11/05 12:33:50 Copyright (C) 2000-2002 Constantin Kaplinsky.

22/11/05 12:33:50 All Rights Reserved.

22/11/05 12:33:50 See http://www.uk.research.att.com/vnc for information on VNC

22/11/05 12:33:50 See http://www.tightvnc.com for TightVNC-specific information

22/11/05 12:33:50 Desktop name 'X' (jnevubuntu:1)

22/11/05 12:33:50 Protocol version supported 3.3

22/11/05 12:33:50 Listening for VNC connections on TCP port 5901

22/11/05 12:33:50 Listening for HTTP connections on TCP port 5801

22/11/05 12:33:50  URL http://jnevubuntu:5801

Font directory '/usr/X11R6/lib/X11/fonts/misc/' not found - ignoring

Font directory '/usr/X11R6/lib/X11/fonts/Speedo/' not found - ignoring

Font directory '/usr/X11R6/lib/X11/fonts/Type1/' not found - ignoring

Font directory '/usr/X11R6/lib/X11/fonts/75dpi/' not found - ignoring

Font directory '/usr/X11R6/lib/X11/fonts/100dpi/' not found - ignoring



Fatal server error:

could not open default font 'fixed'

there's a tutorial on this site for vnc that i'm trying to follow, but i can't because it's giving me these error messages. my xorg.conf is fine, i put in all the stuff i needed for vnc to run. i installed vnc from realvnc and all the packages with vnc in the name from synaptic.

any help would rock.
thanks

i *think* this is down to you running the xorg-x11 server with vnc there expecting to find fonts in the older xfree86 server location. i'm afraid i don't know of a "nice" way to get around this, other than using a possibly newer version, but essentially if you open up the vncserver script, and search for "font" you'll find a line that lists the font path. newer fonts are now placed in /usr/share/fonts i believe, so you can place that path there. you may also be able to speficy the -fp option on the vncserver command line, but i've not looked through the vncserver script enough to know if that option would get passed through or not.

Hi
Just a minor correction to the last post:
The fonts path used by Xorg is /usr/share/X11/fonts
You could also get around this problem by creating a symlink from /usr/X11R6/lib/X11/fonts to /usr/share/X11/fonts

Ian

I remember seeing the solution to this in the FAQ.

The 'fixed' font is needed for the server to start - if it can't find it, you need to specify the correct font path for your machine in the 'vncserver' script. If you're not sure what the path should be, type 'xset q' from within a normal X session. One of the things reported is the font path used by your current X server, which is generally the right thing to use for Xvnc. On some platforms you may need to use a colon as a separator in the font path instead of a comma.

The VNC server can also get upset if you have directories on your font path which don't actually exist on your system. Make sure you remove those. Also note that older versions of the Xvnc server, by default, act as if they had a resolution of 100dpi. Some RedHat installations, for example, only install 75dpi fonts, so you may need to install the missing font RPMs from your distribution or use the -dpi option to Xvnc, or update to the latest version.