TightVNC Server

[Philip Seeger]

How can I find out which bits are missing?

I've added your code to my xstartup file. Then I started a vnc session and
ran "startkde &".
But it's the same problem. This Fedora loading screen just stucks at this
special point.

Btw: Trying "gnome-session &" gives me a window with this error:
"Could not connect to session bus: Did not receive a reply. [...]"

Is this behavior normal? 


-----Original Message-----
From: fedora-list-bounces at redhat.com [mailto:fedora-list-bounces at redhat.com]
On Behalf Of Tom Horsley
Sent: Sunday, August 09, 2009 9:18 PM
To: fedora-list at redhat.com
Subject: Re: TightVNC Server

On Sun, 9 Aug 2009 20:39:01 +0200
Philip Seeger wrote:

> What's wrong here?
> 
> Thanks for your help!

My impression is that both startkde and gnome-session neglect to
actually start some of the bits they need. Everyone for sure
needs a dbus session running, so one of the things that
seems to make vnc startup work better is this fragment:

if [ -z "$DBUS_SESSION_BUS_ADDRESS" ]
then
   echo .xsession starting dbus
   eval `dbus-launch --sh-syntax --exit-with-session`
else
   echo dbus already started
fi

I don't know if that is enough to get kde going as well.

Apparently things like this are started by gdm or kdm rather
than gnome-session or startkde.

-- 
fedora-list mailing list
fedora-list at redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines