TightVNC Server

[Philip Seeger]

Ok, there are news: After a reboot, the error messages from "startkde &" are
different and Gnome works ("gnome-session &") fine!

Here are some error messages:
Could not register with D-Bus aborting.
...
startkde: shutting down
...
can not contact kdeinit4
running shutdown scripts
done

I'm glad that Gnome is working now. But actually I'd prefer KDE.
So, any ideas what to do?

Thanks in advance !



-----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:59 PM
To: fedora-list at redhat.com
Subject: Re: TightVNC Server

On Sun, 9 Aug 2009 21:35:11 +0200
Philip Seeger wrote:

>How can I find out which bits are missing?

I often wonder that :-). One of the things you can do is
a ps to see what you are running when logged into a
normal session directly on the console, but it is hard
to know which of the things you'll see there are started
by gnome-session and which are started by gdm.

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

Weird. That sounds like the error you'd get with no dbus
session, which is exactly what the code was trying to
start.

I just tried to get vnc to start a gnome session, and couldn't
do it, so just dbus doesn't appear to be enough. Perhaps
some of the things in /etc/X11/xinit/xinitrc and
/etc/X11/xinit/xinitrc.d/ are where some essential things
get started? I see the dbus stuff in there, maybe all the
other things are needed as well?

I normally just run a copy of the fvwm window manager with
a few of my own custom apps, so I don't really remember if
I ever got a complete gnome or kde session to work in vnc.

-- 
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