[NBLUG/talk] Problems with X and VNC

[Andrew]

Well, I think I may have made some progress, though I'm still
having problems. I found a Webpage at
http://aolab.phys.dal.ca/~tomduck/linux-ref.html which talks
about the $vncStartup variable in /etc/vnc.conf (it's near the
bottom of the Webpage). In my default vnc.conf, this variable was
commented out, but it was set to "/etc/X11/Xsession". And in my
vncserver script, there is this:

if (!$vncStartup) {
  $vncStartup = "/etc/X11/Xsession";

vncserver even told me that it was using /etc/X11/Xsession:

warn "Starting applications specified in $vncStartup\n";

... although I didn't realize until now that that's not what we
wanted it to do. So now I've set $vncStartup to source my
.vnc/xstartup file. I know it's working because now I *do* get
error messages in my logfile, and they're obviously related to
what I've got in my xstartup.

The logfile:

20/05/03 02:36:09 Xvnc version 3.3.3r2+tight1.2.2
20/05/03 02:36:09 Copyright (C) AT&T Laboratories Cambridge.
20/05/03 02:36:09 All Rights Reserved.
20/05/03 02:36:09 See http://www.uk.research.att.com/vnc for information on VNC
20/05/03 02:36:09 Desktop name 'X' (lhasa:1)
20/05/03 02:36:09 Protocol version supported 3.3
20/05/03 02:36:09 Listening for VNC connections on TCP port 5901
xrdb: No route to host
xrdb: Can't open display 'lhasa:1'
xsetroot:  unable to open display 'lhasa:1'
twm:  unable to open display "lhasa:1"
xterm Xt error: Can't open display: lhasa:1

20/05/03 02:37:03 Got connection from client 192.168.1.3
20/05/03 02:37:03 Protocol version 3.3
20/05/03 02:37:08 Pixel format for client 192.168.1.3:
20/05/03 02:37:08   8 bpp, depth 8
20/05/03 02:37:08   true colour: max r 7 g 7 b 3, shift r 0 g 3 b 6
20/05/03 02:37:08 rfbProcessClientNormalMessage: ignoring unknown encoding 16
20/05/03 02:37:08 Using hextile encoding for client 192.168.1.3
20/05/03 02:37:09 Pixel format for client 192.168.1.3:
20/05/03 02:37:09   16 bpp, depth 16, little endian
20/05/03 02:37:09   true colour: max r 31 g 63 b 31, shift r 11 g 5 b 0
20/05/03 02:37:09   no translation needed
20/05/03 02:37:26 Client 192.168.1.3 gone
20/05/03 02:37:26 Statistics:
20/05/03 02:37:26   key events received 1, pointer events 248
20/05/03 02:37:26   framebuffer updates 247, rectangles 522, bytes 638024
20/05/03 02:37:26     hextile rectangles 522, bytes 638024
20/05/03 02:37:26   raw bytes equivalent 2102452, compression ratio 3.295255


I'm still using this xstartup:

#!/bin/sh
xrdb $HOME/.Xresources
xsetroot -solid grey
exec xterm -geometry 80x24+10+10 -ls &
exec twm &


So what's causing the xrdb problem?

A.