I followed the HOWTO:
(same author) in order to activate the sessionwide part of the dbus-daemon. Great article!
However, using $HOME/.dbus-session relies on the output of dbus-launch. I have installed version 1.0.2, which returns:
which is similar to that stated in the document under the second link above.
The problem is that the statement:
is missing in the output of dbus-launch!!
Hence, when the file $HOME/.dbus-session is sourced, this variable is not published to the other applications and they will fail to identify the DBUS-daemon. Also, the scripts inserted in /etc/session.d/kdm/scripts/... will fail, since $DBUS_SESSION_BUS_PID is empty!
I wonder wether this is a bug of dbus-launch or whether I have to insert the export command manually.