log files for VNC, problem getting service to work on ports :1, :2...

[Jeff Towarnicki]

Here are the log files, for :1, :2, and finaly :3 (the
port which my gnome desktop loads up on... (the other
2 have just a grey background..

[jtowarn@cr787749-a .vnc]$ cat cr787749-a\:1.log
09/01/03 10:20:07 Xvnc version 3.3.3r1
09/01/03 10:20:07 Copyright (C) AT&T Laboratories
Cambridge.
09/01/03 10:20:07 All Rights Reserved.
09/01/03 10:20:07 See
http://www.uk.research.att.com/vnc for information on
VNC
09/01/03 10:20:07 Desktop name 'X' (cr787749-a:1)
09/01/03 10:20:07 Protocol version supported 3.3
09/01/03 10:20:07 Listening for VNC connections on TCP
port 5901
09/01/03 10:20:07 Listening for HTTP connections on
TCP port 5801
09/01/03 10:20:07   URL http://cr787749-a:5801


[jtowarn@cr787749-a .vnc]$ cat cr787749-a\:2.
cr787749-a:2.log  cr787749-a:2.pid
[jtowarn@cr787749-a .vnc]$ cat cr787749-a\:2.log
09/01/03 10:23:02 Xvnc version 3.3.3r1
09/01/03 10:23:02 Copyright (C) AT&T Laboratories
Cambridge.
09/01/03 10:23:02 All Rights Reserved.
09/01/03 10:23:02 See
http://www.uk.research.att.com/vnc for information on
VNC
09/01/03 10:23:02 Desktop name 'X' (cr787749-a:2)
09/01/03 10:23:02 Protocol version supported 3.3
09/01/03 10:23:02 Listening for VNC connections on TCP
port 5902
09/01/03 10:23:02 Listening for HTTP connections on
TCP port 5802
09/01/03 10:23:02   URL http://cr787749-a:5802

[jtowarn@cr787749-a .vnc]$ cat cr787749-a\:3.log
09/01/03 10:23:42 Xvnc version 3.3.3r1
09/01/03 10:23:42 Copyright (C) AT&T Laboratories
Cambridge.
09/01/03 10:23:42 All Rights Reserved.
09/01/03 10:23:42 See
http://www.uk.research.att.com/vnc for information on
VNC
09/01/03 10:23:42 Desktop name 'X' (cr787749-a:3)
09/01/03 10:23:42 Protocol version supported 3.3
09/01/03 10:23:42 Listening for VNC connections on TCP
port 5903
09/01/03 10:23:42 Listening for HTTP connections on
TCP port 5803
09/01/03 10:23:42   URL http://cr787749-a:5803
xrdb: No such file or directory
xrdb: can't open file '/home/jtowarn/.Xresources'
SESSION_MANAGER=local/cr787749-a:/tmp/.ICE-unix/16050

Gtk-WARNING **: gtk_signal_disconnect_by_data(): could
not find handler containing data (0x8153B68)







(oddly enough the 3rd file is the only with a warning,
yet that is where the service works!!!), waht is
causing this to be different from the log files on :1
and :2????

each time I am using the same script, the below
script:

[jtowarn@cr787749-a .vnc]$ cat vncstart
vncserver -depth 24 -geometry 1152x864


and my xstartup file looks like so:

[jtowarn@cr787749-a .vnc]$ cat xstartup
#!/bin/sh

xrdb $HOME/.Xresources
xsetroot -solid grey
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP
Desktop" &
startgnome &



hope that is enough information let me know if I left
anything out,

thanks a million,

Jeff Towarnicki.






----- Original Message -----
From: "Jeff Towarnicki" <jtowarnicki@yahoo.com>
> The thing is, it works on port :3
>
> THat is if I run my vncstart script 3 times, the
first
> :1 gets used, the second time :2 gets used... the
> third time on :3, I can access gnome perfectly fine!
>
> And get this.. it used to work on :1 AND then it
broke
> on there (all of the sudden turned into a grey
> background, then I started up a new server by
> accident, and used it and it worked on :2 perfectly
> fine.. Then all of the sudden :2 got broken, and
gnome
> didn't work on this anymore, so you guessed it I am
> onto port :3 now..... I have not changed anything in
> the system, nothing in the firewall script...
>
> Even after re-boots of the X machine I still can't
use
> :1 or :2 with the gnome desktop, only again after I
> start the same script a third time and it moves onto
> :3 ??? and after a reboot no X server is run my
thing
> starts up in init level 3 like it always has, and I
> have no rc.d file to start vnc either.. THis problem
> is realy bothering me.


I understand the situation.  You answered the first
question, you are 
using
Gnome.  Now please answer the second question and tell
us what the VNC 
logs
say.

Since you are getting a display and mouse cursor, VNC
is working.  Your
window manager is not.  This is the case with 99% of
the "problems" 
with
VNC.  You are not an exception.

BTW - Please reply to the list.  It makes it much
easier on those of us 
with
filters, and I don't have to quote so much to keep
everyone else in the
loop.

--
William Hooper

I don't suffer from insanity, I enjoy every minute of
it
_______________________________________________

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com