From owner-freebsd-questions Wed Nov 11 05:52:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA17314 for freebsd-questions-outgoing; Wed, 11 Nov 1998 05:52:19 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA17309 for ; Wed, 11 Nov 1998 05:52:17 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.8/8.8.4) with ESMTP id IAA02088; Wed, 11 Nov 1998 08:51:57 -0500 (EST) Received: from lakes.dignus.com (lakes [10.0.0.3]) by dignus.com (8.8.8/8.8.5) with ESMTP id JAA27366; Wed, 11 Nov 1998 09:39:46 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.8.8/8.6.9) id IAA01045; Wed, 11 Nov 1998 08:53:11 -0500 (EST) Date: Wed, 11 Nov 1998 08:53:11 -0500 (EST) From: Thomas David Rivers Message-Id: <199811111353.IAA01045@lakes.dignus.com> To: rdmurphy@vt.edu, rivers@dignus.com Subject: Re: vnc Fatal server error: could not open default cursor font 'cursor' Cc: FreeBSD-questions@FreeBSD.ORG In-Reply-To: <199811102223.RAA16868@neale.econ.vt.edu> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Maybe I'm both missing something and making things less clear. The > true(verbatim) log file is: > > 10/11/98 15:40:01 Xvnc version 3.3.2r2 > 10/11/98 15:40:01 Copyright (C) 1997-8 Olivetti & Oracle Research Laboratory > 10/11/98 15:40:01 See http://www.orl.co.uk/vnc for information about VNC > 10/11/98 15:40:01 Desktop name 'X' (neale.econ.vt.edu:1) > 10/11/98 15:40:01 Protocol version supported 3.3 > 10/11/98 15:40:01 Listening for VNC connections on TCP port 5901 > 10/11/98 15:40:01 Listening for HTTP connections on TCP port 5801 > 10/11/98 15:40:01 URL http://neale.econ.vt.edu:5801 > > Fatal server error: > could not open default cursor font 'cursor' > _X11TransSocketINETConnect: Can't connect: errno = 61 > _X11TransSocketINETConnect: Can't connect: errno = 61 > _X11TransSocketINETConnect: Can't connect: errno = 61 > _X11TransSocketINETConnect: Can't connect: errno = 61 > _X11TransSocketINETConnect: Can't connect: errno = 61 > _X11TransSocketINETConnect: Can't connect: errno = 61 > xrdb: Interrupted system call > xrdb: Can't open display 'neale.econ.vt.edu:1' > _X11TransSocketINETConnect: Can't connect: errno = 61 > _X11TransSocketINETConnect: Can't connect: errno = 61 > _X11TransSocketINETConnect: Can't connect: errno = 61 > _X11TransSocketINETConnect: Can't connect: errno = 61 > _X11TransSocketINETConnect: Can't connect: errno = 61 > _X11TransSocketINETConnect: Can't connect: errno = 61 > xsetroot: unable to open display 'neale.econ.vt.edu:1' > _X11TransSocketINETConnect: Can't connect: errno = 61 > _X11TransSocketINETConnect: Can't connect: errno = 61 > _X11TransSocketINETConnect: Can't connect: errno = 61 > _X11TransSocketINETConnect: Can't connect: errno = 61 > _X11TransSocketINETConnect: Can't connect: errno = 61 > _X11TransSocketINETConnect: Can't connect: errno = 61 > _X11TransSocketINETConnect: Can't connect: errno = 61 > _X11TransSocketINETConnect: Can't connect: errno = 61 > _X11TransSocketINETConnect: Can't connect: errno = 61 > _X11TransSocketINETConnect: Can't connect: errno = 61 > _X11TransSocketINETConnect: Can't connect: errno = 61 > _X11TransSocketINETConnect: Can't connect: errno = 61 > xterm Xt error: Can't open display: neale.econ.vt.edu:1 > twm: unable to open display "neale.econ.vt.edu:1" > > > My interpretation of this is that vncserver is trying to find "cursor > font 'cursor'", and not finding it, dies. Therefore, the connection > refused errno is simply a symptom of the server which doesn't start > (properly). In /usr/X11R6/lib/X11/fonts/misc, there is a file > cursor.pcf.gz. This directory is in the font path specified by the > vncserver script. Yes - but an X11 client doesn't look at the file; it sends an X11 protocol message to the X server; asking it for the font. And, since you can't talk to the X server, the font isn't found. I think it's because you don't have a :1 X server running, just a :0 one... that is, you have an X server listing on port 6000, just don't have one listening on port 6001. - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message