Subject: Suse112 as vserver: Could not start D-Bus. Can you call qdbus?
From: Ekkard Gerlach <ekkardgerlach@aiai.de>
Date: Sun, 13 Nov 2011 12:22:43 +0100

Hi, 

debian squeeze is host, Suse11.2 is running als vserver. Other clients in 
the LAN make XDMCP on Suse 11.2. KDM starts, I can type name and password, 
but the the xmessage "Could not start D-Bus. Can you call qdbus?" appears and
I'm back in KDM.

suse112:~ # ps ax
  PID TTY      STAT   TIME COMMAND
    1 ?        Ss     0:01 init [2]
 2366 ?        Ss     0:00 /bin/dbus-daemon --system
 2389 ?        Ss     0:00 /usr/sbin/sshd -o PidFile=/var/run/sshd.init.pid
 2396 ?        Ss     0:00 /usr/bin/kdm
 2417 ?        Sl     0:00 /sbin/rsyslogd -c 4 -f /etc/rsyslog.conf
 2441 ?        Ss     0:00 /sbin/rpcbind
 2452 ?        Ss     0:00 /usr/sbin/nmbd -D -s /etc/samba/smb.conf
 2545 ?        Ss     0:00 /usr/sbin/cupsd -C /etc/cups/cupsd.conf
 2617 ?        Ss     0:00 /usr/lib/postfix/master
 2655 ?        Ss     0:00 /usr/sbin/cron
 2656 ?        S      0:00 pickup -l -t fifo -u
 2657 ?        S      0:00 qmgr -l -t fifo -u
 2667 ?        S+     0:00 login
 2701 pts/1    Ss     0:00 /bin/bash -login
 2765 pts/1    R+     0:00 ps ax


I've set up in Suse-Yast, that XDM not starts X11, X11 should not 
run in the vserver, only KDM. X is taken from the clients. 
Clients are Suse, Debian with XFCE, Xming under Windows, etc.

# cat /home/<user>/.xsession-errors-rex4.local\:1
xset:  bad font path element (#23), possible causes are:
    Directory does not exist or has wrong permissions
    Directory missing fonts.dir
    Incorrect font server address or syntax
startkde: Starting up...
Failed to start message bus: Failed to bind socket
"/tmp/dbus-9cOQPWPuu6": Address already in use
EOF in dbus-launch reading address from bus daemon
startkde: Could not start D-Bus. Can you call qdbus?


/var/log/messages
Nov 12 21:46:11 suse112 kdm: rex4.local:1[3684]: Client start failed
Nov 12 21:46:11 suse112 kdm: rex4.local:1[3684]: Cannot close ConsoleKit
session: Unable to close session: no session open
Nov 12 21:46:11 suse112 kdm_config[3834]: Multiple occurrences of key
'StaticServers' in section [General] of
/usr/share/kde4/config/kdm/kdmrc
Nov 12 21:46:11 suse112 kdm_config[3834]: Multiple occurrences of key
'UseTheme' in section [X-*-Greeter] of
/usr/share/kde4/config/kdm/kdmrc
Nov 12 21:54:11 suse112 kdm_config[4346]: Multiple occurrences of key
'StaticServers' in section [General] of
/usr/share/kde4/config/kdm/kdmrc
Nov 12 21:54:11 suse112 kdm_config[4346]: Multiple occurrences of key
'UseTheme' in section [X-*-Greeter] of
/usr/share/kde4/config/k

These error messages are wrong, 'StaticServers' etc. does not occur multiple 
in kdmrc. kdmrc is untouched.

# init 5
init: /dev/initctl: No such file or directory

so I did     mkfifo /dev/initctl , the  /dev/initctl  seems so rest
permanently, even after a reboot. But runlevel 5 is not reached. 
BTW: I don't need runlevel 5, the links of kdm/xdm and dbus in rc5.d are 
now copied to rc3.d. 

The qt-dbus seems to the sticking point, it does'nt start:

suse112:/ # /usr/bin/qdbus
Could not connect to D-Bus server:
org.freedesktop.DBus.Error.Spawn.ExecFailed: /bin/dbus-launch terminated
abnormally with the
following error: Autolaunch error: X11 initialization failed.

Does qdbus want to start X11? - I configured in yast that KDM should not 
start X11. Where can I check whether yast did it correctly? 

Who can help?

tia
Ekkard