VNC seems to cause GNOME apps to not be able to open
tfseak "at" futurmaster.com
Tue Jun 1 11:23:00 2004
Are your RedHat and GNOME the latest version? Have you asked the same questions in GNOME newsgroup?
> -----Message d'origine-----
> De : Michael Matthews [mailto:mlmatthews "at" hotmail.com]
> Envoyi : samedi 29 mai 2004 00:20
> @ : vnc-list "at" realvnc.com
> Objet : VNC seems to cause GNOME apps to not be able to open network sockets
> Fri 2004-MAY-28 1519 PDT
> I am running Red Hat 8.0 Linux on a workstation. I am using GNOME for the
> desktop manager at the console (I don't know how to find out what version it
> is, but it is the version installed with Red Hat 8.0). I run VNC 3.3.7 on
> screen :1 and have it configured to use the KDE 3.0.3 desktop manager (KDE
> absolutely refuses to have more than one instance of itself running on the
> same host).
> I have noticed a problem with the GNOME desktop at the console. After
> logging into the console of my Linux workstation, opening terminal windows
> and applications from the Panel is fine. As soon as I run a VNC server with
> "vncserver" (which starts a VNC server on screen :1), it takes about six to
> ten seconds for an application to open after being clicked in the Panel.
> I opened a terminal and executed "tail -f .xsession-errors" to see if any
> kind of errors were happening with the X applications. After clicking on a
> GNOME application in the Panel (like gnome-terminal or
> gnome-system-monitor), I have to wait about six seconds and then the
> application will be displayed. The .xsession-errors file then records the
> following error:
> (gnome-terminal:15404): GnomeUI-WARNING **: While connecting to session
> Could not open network socket.
> If I launch a KDE application from GNOME, I have to wait for the same period
> of time and then the application will be displayed, with the following error
> in the .xsession-errors file:
> DCOPServer up and running.
> Session management error: Could not open network socket
> I suspect the that delay is the application timing out when it tries to open
> some network socket.
> When I am using the VNC session from a VNC client, I have no delays when
> launching either GNOME or KDE applications from the KDE Lanchbar.
> In order to get rid of the launching delays, I have to kill the VNC server,
> logout of GNOME, and then log back in.
> My HOME directory is NFS mounted from a server with automounter. This is so
> I can log into different Linux workstations and have the same HOME
> My question is why is VNC interfering with the GNOME network sockets and how
> can I fix this problem so I don't have such a long delay when launching
> applications in GNOME?
> System-specific information:
> Red Hat version:
> uname -a
> Linux lnxvcmm02.vcd.hp.com 2.4.18-14 #1 Wed Sep 4 13:35:50 EDT 2002 i686
> i686 i386 GNU/Linux
> cat /etc/redhat-release
> Red Hat Linux release 8.0 (Psyche)
> VNC version : 3.3.7
> VNC "xstartup" file:
> cat ~/.vnc/xstartup
> [ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
> xsetroot -solid grey
> # xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
> # twm &
> # Use this line to start GNOME
> # /usr/bin/gnome-session &
> # Use this line to start KDE
> /usr/bin/startkde &
> Stop worrying about overloading your inbox - get MSN Hotmail Extra Storage!
> VNC-List mailing list
> VNC-List "at" realvnc.com
> To remove yourself from the list visit: