Hello,
I followed the HOWTO:
http://www.howtoforge.com/dbus_kde_integration or
http://linux.bononline.nl/linux/sess.../example03.php
(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:
"DBUS_SESSION_BUS_ADDRESS='unix:abstract=/tmp/dbus-HIociAdxIN,guid=d9be034529991a393dde1ae11b9b3000';
export DBUS_SESSION_BUS_ADDRESS;
DBUS_SESSION_BUS_PID=3679;"
which is similar to that stated in the document under the second link above.
The problem is that the statement:
export DBUS_SESSION_BUS_PID;
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.
Nanko
Recent comments
1 day 4 hours ago
1 day 9 hours ago
1 day 13 hours ago
1 day 15 hours ago
2 days 5 hours ago
2 days 5 hours ago
2 days 10 hours ago
2 days 17 hours ago
2 days 18 hours ago
2 days 19 hours ago