Bug 216402

Version:            (using KDE 4.3.1)
OS:                Linux
Installed from:    openSUSE RPMs

Server
System:		LINUX openSUSE 11.2
Desktop:	KDE 4.3
Problem:	KDE cannot be started with startkde from a virtual X Window Session.
		Case a: vncserver is started as standard user,
		DISPLAY environment variable value other than :0.0
		causes an error.
		Case b: vncserver is started as root,
		dbus is not available.
Case a
------
Step1:		Starting vncserver as user axel: 
		New 'X' desktop is Haydn:5
Step2:		Starting vncviewer (Web): http:/haydn:5805
		For this the script /home/axel/.vnc/xstartup is used
		that opens an xterm
Step3:		Starting KDE with script startkde
		the openSUSE start screen can be seen shortly,
		but then the following error messages appear:

axel~> startkde
startkde: Starting up...
kdeinit4: preparing to launch /usr/lib/libkdeinit4_klauncher.so
kdeinit4: Communication error with launcher. Exiting!
kdeinit4_wrapper: Warning: connect(/home/axel/.kde4/socket-Haydn/kdeiniled: : Connection refused
Could not register with D-BUS. Aborting.
startkde: Shutting down...
kdeinit4_wrapper: Warning: connect(/home/axel/.kde4/socket-Haydn/kdeiniled: : Connection refused
Error: Can not contact kdeinit4!
startkde: Running shutdown scripts...
startkde: Done.
axel~>

Analysis:	In script startkde the the program
		/usr/lib/kde4/libexec/start_kdeinit_wrapper
   				+kcminit_startup
		is called. This routine works with value
		$DISPLAY=:0.0 but not with value $DISPLAY=:5.0 
		that has to be used here.
	
Case b
------
Step4:		Starting vncserver as user root: New 'X' desktop is 
		Haydn:5

Step5:		Starting vncviewer (Web): http:/haydn:5805
		For this the script /root/.vnc/xstartup is used 
		that opens an xterm

Step6:		Starting KDE with script startkde
		the openSUSE start screen can be seen shortly, 
		but then the following d-bus error message appears:

# startkde
startkde: Starting up...
startkde: Could not start D-Bus. Can you call qdbus?

# qdbus
Could not connect to D-Bus server: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.