It seems odd here since I can't start any xclient apparently. I've been
running my own install of vnc on several boxes with no problem for ages.
I'm wondering if something needs to be chmod'd to get it to work right,
although I've tried as a normal user and as root.
On Sun, 14 Jan 2001, Mark Belanger wrote:
> I'm positive that vnc works with windowmaker and kde in
> Mandrake 7.2
>
> -Mark
>
> "John J. LeMay Jr." wrote:
> >
> > I cannot seem to get a window manager to start with the VNC package that
> > shipped with LM 7.2. I've tried using gnome-session and twm & in
> > ~/.vnc/xstartup, but neither will start. Ever tried starting gnome-terminal,
> > that didn't work either. Here's a copy of the log:
> >
> > 13/01/01 19:03:30 Xvnc version 3.3.3
> > 13/01/01 19:03:30 Copyright (C) 1999 AT&T Laboratories Cambridge.
> > 13/01/01 19:03:30 All Rights Reserved.
> > 13/01/01 19:03:30 See http://www.uk.research.att.com/vnc for information on VNC
> > 13/01/01 19:03:30 Desktop name 'X' (cyclops:1)
> > 13/01/01 19:03:30 Protocol version supported 3.3
> > 13/01/01 19:03:30 Listening for VNC connections on TCP port 5901
> > 13/01/01 19:03:30 Listening for HTTP connections on TCP port 5801
> > 13/01/01 19:03:30 URL http://cyclops:5801
> > X connection to cyclops:1.0 broken (explicit kill or server shutdown).
> >
> > 13/01/01 19:03:57 Got connection from client 192.168.2.51
> > 13/01/01 19:03:57 Protocol version 3.3
> > 13/01/01 19:04:00 Pixel format for client 192.168.2.51:
> > 13/01/01 19:04:00 32 bpp, depth 24, little endian
> > 13/01/01 19:04:00 true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0
> > 13/01/01 19:04:00 Using hextile encoding for client 192.168.2.51
> > 13/01/01 19:04:04 Client 192.168.2.51 gone
> > 13/01/01 19:04:04 Statistics:
> > 13/01/01 19:04:04 key events received 1, pointer events 45
> > 13/01/01 19:04:04 framebuffer updates 47, rectangles 96, bytes 410268
> > 13/01/01 19:04:04 hextile rectangles 96, bytes 410268
> > 13/01/01 19:04:04 raw bytes equivalent 3225900, compression ratio 7.862909
> >
> > Looks like X is lost right after starting the http listener.
> >
> > Any ideas?
> >
> > Thanks!
> >
> > John LeMay Jr.
> > Senior Enterprise Consultant
> > NJMC, LLC.
>
