%general-entities; ]> $LastChangedBy$ $Date$ dbus-launch D-Bus was installed in LFS, but one program needs to be updated after Xorg is installed to properly support window managers. Package Information Download (HTTP): Download (FTP): Download MD5 sum: &dbus-md5sum; Download size: &dbus-size; Estimated disk space required: &dbus-buildsize; Estimated build time: &dbus-time; D-Bus Dependencies Required (for dbus-launch program) Optional For the tests: , , and ; for the API documentation: ; for man pages and XML/HTML documentation: User Notes: Build D-Bus by running the following commands: ./configure --prefix=/usr \ --sysconfdir=/etc \ --localstatedir=/var \ --with-console-auth-dir=/run/console/ \ --disable-static && make See below for test instructions. Now, as the root user: install -m 755 tools/dbus-launch /usr/bin If you built the optional documentation, install it as the root user: cp -a doc/api/{html,xml} /usr/share/doc/dbus-&dbus-version; The dbus tests cannot be run until after has been installed. They must be run as an unprivileged user from a local session. Tests fail through ssh. If you want to run only the unit tests, replace, below, --enable-tests by --enable-embedded-tests, otherwise, has to be installed, before. The tests require passing additional parameters to configure and exposing additional functionality in the binaries. These interfaces are not intended to be used in a production build of D-Bus. If you would like to run the tests, issue the following commands: make distclean && ./configure --enable-tests --enable-asserts && make && make check && make distclean If run-test.sh fails, it can be disabled with the following sed, before running the commands for the tests: sed -i -e 's:run-test.sh:$(NULL):g' test/name-test/Makefile.in There has been a report that the tests may fail if running inside a Midnight Commander shell. You may get out-of-memory error messages when running the tests. These are normal and can be safely ignored. --with-console-auth-dir=/run/console/: This parameter specifies location of the ConsoleKit auth dir. --enable-tests: Build extra parts of the code to support all tests. Configure will end with a NOTE warning about increased size of libraries and decreased security. --enable-embedded-tests: Build extra parts of the code to support only unit tests. Configure will end with a NOTE warning about increased size of libraries and decreased security. --enable-asserts: Enable debugging code to run assertions for statements normally assumed to be true. This prevents a warning that '--enable-tests' on its own is only useful for profiling and might not give true results for all tests, but adds its own NOTE that this should not be used in a production build. /etc/dbus-1/session.conf, /etc/dbus-1/system.conf and /etc/dbus-1/system.d/* /etc/dbus-1/session.conf /etc/dbus-1/system.conf /etc/dbus-1/system.d/* The configuration files listed above should probably not be modified. If changes are required, you should create /etc/dbus-1/session-local.conf and/or /etc/dbus-1/system-local.conf and make any desired changes to these files. If any packages install a D-Bus .service file outside of the standard /usr/share/dbus-1/services directory, that directory should be added to the local session configuration. For instance, /usr/local/share/dbus-1/services can be added by performing the following commands as the root user: cat > /etc/dbus-1/session-local.conf << "EOF" <!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN" "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd"> <busconfig> <!-- Search for .service files in /usr/local --> <servicedir>/usr/local/share/dbus-1/services</servicedir> </busconfig> EOF There are many methods you can use to start a session daemon using the dbus-launch command. Review the dbus-launch man page for details about the available parameters and options. Here are some suggestions and examples: Add dbus-launch to the line in the ~/.xinitrc file that starts your graphical desktop environment. If you use xdm or some other display manager that calls the ~/.xsession file, you can add dbus-launch to the line in your ~/.xsession file that starts your graphical desktop environment. The syntax would be similar to the example in the ~/.xinitrc file. The examples shown previously use dbus-launch to specify a program to be run. This has the benefit (when also using the --exit-with-session parameter) of stopping the session daemon when the specified program is stopped. You can also start the session daemon in your system or personal startup scripts by adding the following lines: # Start the D-Bus session daemon eval `dbus-launch` export DBUS_SESSION_BUS_ADDRESS This method will not stop the session daemon when you exit your shell, therefore you should add the following line to your ~/.bash_logout file: # Kill the D-Bus session daemon kill $DBUS_SESSION_BUS_PID A hint has been written that provides ways to start scripts using the KDM session manager of KDE. The concepts in this hint could possibly be used with other session managers as well. The hint is located at . Installed Programs Installed Libraries Installed Directories dbus-launch None None Short Descriptions dbus-launch is used to start dbus-daemon from a shell script. It would normally be called from a user's login scripts. dbus-launch