Hello, I followed the HOWTO: http://www.howtoforge.com/dbus_kde_integration or http://linux.bononline.nl/linux/sessionscripts/02/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
dbus error: no export for pid var??? Hello, first thanks for your feedback! Second in my version (0.62) there is also no export for the variable DBUS_SESSION_BUS_PID. But the scripts I've written can handle that. When sourcing the ~/.dbus-session file, the variable is set. No explicit export command is necessary. When you open a new bashsession, and source the file in your homedirectory you'll see this. Why the scripts run into trouble I do not know. Stef
