On Sun, Nov 13, 2011 at 12:22:43PM +0100, Ekkard Gerlach wrote: > Hi, > debian squeeze is host, Suse11.2 is running als vserver. as I see, you have a number of partially unrelated issues and you've definitely chosen a host distro which probably will give you a lot more trouble (due to outdated and broken packages) than necessary ... in any case: what kernel/patch/util-vserver version do you use? > 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. you're aware that xdm/gdm/kdm require an X11 to display on, so they 'normally' start one (or a number of them) read: I have no clue what you plan to do :) > # 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. at least gdm sources a lot more config files than just the 'one and only' main config file, so I'd check for (maybe hidden) includes and other places where kdm configs might reside (strace -fF should help with that) > # init 5 > init: /dev/initctl: No such file or directory if there is no initctl, chances are good that your guest doesn't have/run a real init process, in which case that is not unexpected ... > 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. a fifo where nobody listens is practically useless i.e. similar to /dev/null and for initless guests, you can select the runlevel in the guest config > 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? no idea, that seems to be suse specific and I stopped using suse a long time ago ... but maybe somebody knows (again strace -fF might be of help) best, Herbert > Who can help? > tia > Ekkard