Ubuntu
tightvnc package

installing tightvncserver should install xfonts-base

Bug #269573 reported by JeremyChapman
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
tightvnc (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: tightvncserver

This is an old one, but I cannot find a report for it, and was surprised it is still a problem.

To reproduce:
Install ubuntu minimal, do 'apt-get install tightvncserver', then try and start it with 'vncserver'.

--------
Result: Couldn't start Xtightvnc; trying default font path.
Please set correct fontPath in the vncserver script.
Couldn't start Xtightvnc process.

12/09/08 16:18:55 Xvnc version 3.3.tight1.2.9
12/09/08 16:18:55 Copyright (C) 1999 AT&T Laboratories Cambridge.
12/09/08 16:18:55 Copyright (C) 2000-2002 Constantin Kaplinsky.
12/09/08 16:18:55 All Rights Reserved.
12/09/08 16:18:55 See http://www.uk.research.att.com/vnc for information on VNC
12/09/08 16:18:55 See http://www.tightvnc.com for TightVNC-specific information
12/09/08 16:18:55 Desktop name 'X' (ubuntu:1)
12/09/08 16:18:55 Protocol version supported 3.3
12/09/08 16:18:55 Listening for VNC connections on TCP port 5901
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
Font directory '/usr/share/fonts/X11/misc/' not found - ignoring
Font directory '/usr/share/fonts/X11/Type1/' not found - ignoring
Font directory '/usr/share/fonts/X11/75dpi/' not found - ignoring
Font directory '/usr/share/fonts/X11/100dpi/' not found - ignoring

Fatal server error:
could not open default font 'fixed'
12/09/08 16:18:56 Xvnc version 3.3.tight1.2.9
12/09/08 16:18:56 Copyright (C) 1999 AT&T Laboratories Cambridge.
12/09/08 16:18:56 Copyright (C) 2000-2002 Constantin Kaplinsky.
12/09/08 16:18:56 All Rights Reserved.
12/09/08 16:18:56 See http://www.uk.research.att.com/vnc for information on VNC
12/09/08 16:18:56 See http://www.tightvnc.com for TightVNC-specific information
12/09/08 16:18:56 Desktop name 'X' (ubuntu:1)
12/09/08 16:18:56 Protocol version supported 3.3
12/09/08 16:18:56 Listening for VNC connections on TCP port 5901
Font directory '/usr/share/fonts/X11/misc/' not found - ignoring
Font directory '/usr/share/fonts/X11/Speedo/' not found - ignoring
Font directory '/usr/share/fonts/X11/Type1/' not found - ignoring
Font directory '/usr/share/fonts/X11/75dpi/' not found - ignoring
Font directory '/usr/share/fonts/X11/100dpi/' not found - ignoring

Fatal server error:
could not open default font 'fixed'

----
root@ubuntu:~# lsb_release -rd
Description: Ubuntu 8.04.1
Release: 8.04
----
root@ubuntu:~# apt-cache policy tightvncserver
tightvncserver:
  Installed: 1.2.9-22
  Candidate: 1.2.9-22
  Version table:
 *** 1.2.9-22 0
        500 http://us.archive.ubuntu.com hardy/universe Packages
        100 /var/lib/dpkg/status
----
Expected: vncserver to start
----
What happens: refuses to start since it cannot find fixed font
=========

Fix is simply to install xfonts-base, which aptitude installs as a 'recommended' package. However, it should be a dependency from my point of view since package will not work otherwise.

Revision history for this message
Rachel Greenham (rachel-strangenoises) wrote :

Actually, having xbase-fonts installed doesn't help. Trying repeatedly to reinstall it doens't help. It probably also doesn't help that, when xbase-fonts is installed, dpkg -L xbase-fonts lists files that aren't there.

rachel@twilight:~$ tightvncserver -nolisten tcp :1
Couldn't start Xtightvnc; trying default font path.
Please set correct fontPath in the tightvncserver script.
Couldn't start Xtightvnc process.

18/11/14 14:05:34 Xvnc version TightVNC-1.3.10
18/11/14 14:05:34 Copyright (C) 2000-2009 TightVNC Group
18/11/14 14:05:34 Copyright (C) 1999 AT&T Laboratories Cambridge
18/11/14 14:05:34 All Rights Reserved.
18/11/14 14:05:34 See http://www.tightvnc.com/ for information on TightVNC
18/11/14 14:05:34 Desktop name 'X' (twilight:1)
18/11/14 14:05:34 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t
18/11/14 14:05:34 Listening for VNC connections on TCP port 5901
Font directory '/usr/share/fonts/X11/75dpi/' not found - ignoring
Font directory '/usr/share/fonts/X11/100dpi/' not found - ignoring

Fatal server error:
could not open default font 'fixed'
18/11/14 14:05:35 Xvnc version TightVNC-1.3.10
18/11/14 14:05:35 Copyright (C) 2000-2009 TightVNC Group
18/11/14 14:05:35 Copyright (C) 1999 AT&T Laboratories Cambridge
18/11/14 14:05:35 All Rights Reserved.
18/11/14 14:05:35 See http://www.tightvnc.com/ for information on TightVNC
18/11/14 14:05:35 Desktop name 'X' (twilight:1)
18/11/14 14:05:35 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t
18/11/14 14:05:35 Listening for VNC connections on TCP port 5901
Font directory '/usr/share/fonts/X11/Speedo/' not found - ignoring
Font directory '/usr/share/fonts/X11/75dpi/' not found - ignoring
Font directory '/usr/share/fonts/X11/100dpi/' not found - ignoring

Fatal server error:
could not open default font 'fixed'

rachel@twilight:~$ apt-cache policy xfonts-base
xfonts-base:
  Installed: 1:1.0.3
  Candidate: 1:1.0.3
  Version table:
 *** 1:1.0.3 0
        500 http://gb.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
        100 /var/lib/dpkg/status
rachel@twilight:~$ dpkg -L xfonts-base | tail -1
/etc/X11/fonts/misc/xfonts-base.alias
rachel@twilight:~$ ls -l /etc/x11/fonts/misc/xfonts-base.alias
ls: cannot access /etc/x11/fonts/misc/xfonts-base.alias: No such file or directory

what a mess.

(14.10)

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in tightvnc (Ubuntu):
status: New → Confirmed
Revision history for this message
pokexpert30@gmail.com (pokexpert30) wrote :

Minor problem. But it shouldn't be a problem to fix it...

Revision history for this message
liudonghua (liudonghua123) wrote :
Download full text (23.1 KiB)

I have the same font warning problem.

The following are some of my terminal contents.

liudonghua@desktop-ldh:~/.vnc$ cat desktop-ldh\:1.log
11/10/18 09:07:32 Xvnc version TightVNC-1.3.10
11/10/18 09:07:32 Copyright (C) 2000-2009 TightVNC Group
11/10/18 09:07:32 Copyright (C) 1999 AT&T Laboratories Cambridge
11/10/18 09:07:32 All Rights Reserved.
11/10/18 09:07:32 See http://www.tightvnc.com/ for information on TightVNC
11/10/18 09:07:32 Desktop name 'X' (desktop-ldh:1)
11/10/18 09:07:32 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t
11/10/18 09:07:32 Listening for VNC connections on TCP port 5901
Font directory '/usr/share/fonts/X11/75dpi/' not found - ignoring
Font directory '/usr/share/fonts/X11/100dpi/' not found - ignoring

11/10/18 09:07:47 Got connection from client 113.55.127.140
11/10/18 09:07:47 Using protocol version 3.8
11/10/18 09:07:47 Full-control authentication passed by 113.55.127.140
11/10/18 09:07:47 rfbProcessClientNormalMessage: ignoring unknown encoding 24
11/10/18 09:07:47 rfbProcessClientNormalMessage: ignoring unknown encoding 16
11/10/18 09:07:47 rfbProcessClientNormalMessage: ignoring unknown encoding 22
11/10/18 09:07:47 rfbProcessClientNormalMessage: ignoring unknown encoding 21
11/10/18 09:07:47 rfbProcessClientNormalMessage: ignoring unknown encoding 15
11/10/18 09:07:47 Using zlib encoding for client 113.55.127.140
11/10/18 09:07:47 rfbProcessClientNormalMessage: ignoring unknown encoding -314
11/10/18 09:07:47 Enabling full-color cursor updates for client 113.55.127.140
11/10/18 09:07:47 rfbProcessClientNormalMessage: ignoring unknown encoding -223
11/10/18 09:07:47 Pixel format for client 113.55.127.140:
11/10/18 09:07:47 8 bpp, depth 6
11/10/18 09:07:47 true colour: max r 3 g 3 b 3, shift r 4 g 2 b 0
11/10/18 09:07:47 Using raw encoding for client 113.55.127.140
11/10/18 09:07:47 rfbProcessClientNormalMessage: ignoring unknown encoding 24
11/10/18 09:07:47 rfbProcessClientNormalMessage: ignoring unknown encoding 22
11/10/18 09:07:47 rfbProcessClientNormalMessage: ignoring unknown encoding 21
11/10/18 09:07:47 rfbProcessClientNormalMessage: ignoring unknown encoding 16
11/10/18 09:07:47 rfbProcessClientNormalMessage: ignoring unknown encoding 15
11/10/18 09:07:47 rfbProcessClientNormalMessage: ignoring unknown encoding -314
11/10/18 09:07:47 Enabling full-color cursor updates for client 113.55.127.140
11/10/18 09:07:47 rfbProcessClientNormalMessage: ignoring unknown encoding -223
11/10/18 09:07:47 rfbProcessClientNormalMessage: ignoring unknown encoding 24
11/10/18 09:07:47 rfbProcessClientNormalMessage: ignoring unknown encoding 16
11/10/18 09:07:47 rfbProcessClientNormalMessage: ignoring unknown encoding 22
11/10/18 09:07:47 rfbProcessClientNormalMessage: ignoring unknown encoding 21
11/10/18 09:07:47 rfbProcessClientNormalMessage: ignoring unknown encoding 15
11/10/18 09:07:47 Using zlib encoding for client 113.55.127.140
11/10/18 09:07:47 rfbProcessClientNormalMessage: ignoring unknown encoding -314
11/10/18 09:07:47 Enabling full-color cursor updates for client 113.55.127.140
11/10/18 09:07:47 rfbProcessClientNormalMessage: ignoring unknown encoding -223
11/10/18 09:07:47 Pixel format for cl...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.