Bug#365593: tightvncserver: Default font path not found
Ian Wienand
Version: 1.3.9-1
Followup-For: Bug #365593
This is not working for me. AFAIK I didn't do anything...
wienandi@coopers:~$ tightvncserver
Couldn't start Xtightvnc; trying default font path.
Please set correct fontPath in the tightvncserver script.
Couldn't start Xtightvnc process.
21/04/08 19:40:10 Xvnc version TightVNC-1.3.9
21/04/08 19:40:10 Copyright (C) 2000-2007 TightVNC Group
21/04/08 19:40:10 Copyright (C) 1999 AT&T Laboratories Cambridge
21/04/08 19:40:10 All Rights Reserved.
21/04/08 19:40:10 See http://www.tightvnc.com/ for information on TightVNC
21/04/08 19:40:10 Desktop name 'X' (coopers:1)
21/04/08 19:40:10 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t
21/04/08 19:40:10 Listening for VNC connections on TCP port 5901
_FontTransSocketUNIXConnect: Can't connect: errno = 2
failed to set default font path 'unix/:7100'
Fatal server error:
could not open default font 'fixed'
21/04/08 19:40:11 Xvnc version TightVNC-1.3.9
21/04/08 19:40:11 Copyright (C) 2000-2007 TightVNC Group
21/04/08 19:40:11 Copyright (C) 1999 AT&T Laboratories Cambridge
21/04/08 19:40:11 All Rights Reserved.
21/04/08 19:40:11 See http://www.tightvnc.com/ for information on TightVNC
21/04/08 19:40:11 Desktop name 'X' (coopers:1)
21/04/08 19:40:11 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t
21/04/08 19:40:11 Listening for VNC connections on TCP port 5901
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'
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.24-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages tightvncserver depends on:
ii libc6 2.7-10 GNU C Library: Shared libraries
ii libjpeg62 6b-14 The Independent JPEG Group's JPEG
ii libx11-6 2:1.0.3-7 X11 client-side library
ii libxext6 2:1.0.4-1 X11 miscellaneous extension librar
ii perl 5.8.8-12 Larry Wall's Practical Extraction
ii x11-common 1:7.3+10 X Window System (X.Org) infrastruc
ii xbase-clients 1:7.3+10 miscellaneous X clients - metapack
ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime
Versions of packages tightvncserver recommends:
ii xfonts-base 1:1.0.0-5 standard fonts for X
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Ola Lundqvist
thanks
Hi
How do your X configuration file look like?
I can see the following from below:
> failed to set default font path 'unix/:7100'
> Fatal server error:
> could not open default font 'fixed'
If you remove that from your config file, do it work then?
Best regards,
// Ola
--
--------------------- Ola Lundqvist ---------------------------
/ op...@debian.org Annebergsslingan 37 \
| o...@inguza.com 654 65 KARLSTAD |
| http://inguza.com/ +46 (0)70-332 1551 |
\ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 /
---------------------------------------------------------------
Ian Wienand
> How do your X configuration file look like?
Ahh, mea culpa, that's the problem. Somehow the following got in there:
# RgbPath is the location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
# Multiple FontPath entries are allowed (they are concatenated together)
# By default, Red Hat 6.0 and later now use a font server independent of
# the X server to render fonts.
RgbPath "/usr/X11R6/lib/X11/rgb"
FontPath "unix/:7100"
Thinking about it, I might have copied someone else's xorg.conf when
setting up, and forgot about it.
Sorry about the false alarm,
-i