From Wikipedia, the free encyclopedia
  (Redirected from D-bus)
Jump to: navigation, search
"DBus" redirects here. It is not to be confused with Dbus.
Developer(s) Red Hat and the community
Stable release 1.8.12[1] / November 24, 2014; 33 days ago (2014-11-24)
Written in C
Operating system Cross-platform
License GNU GPL version 2 or later, or AFL 2.1[2]
Website www.freedesktop.org/wiki/Software/dbus

D-Bus is a free and open-source inter-process communication (IPC) system, allowing multiple, concurrently-running computer programs (processes) to communicate with one another.

D-Bus provides the following functionality:

  • communication between desktop applications in the same desktop session; to allow integration of the desktop session as a whole, and address issues of the process lifecycle
  • communication between the desktop session and the operating system, where the operating system would typically include the kernel and any system daemons or processes

Heavily influenced by the DCOP system used by versions 2 and 3 of KDE, D-Bus has replaced DCOP in the KDE 4 release. An implementation of D-Bus supports most POSIX operating systems, and a port for Windows exists. It is used by Qt 4 and GNOME. In GNOME it has gradually replaced most parts of the earlier Bonobo mechanism. It is also used by Xfce.

D-Bus is developed as part of the freedesktop.org project.


D-Bus is a message bus system, or a medium for interprocess communication that allows the applications to communicate and exchange messages between themselves. Thus, D-Bus provides additional or simplifies existing functionality to the applications, including information sharing, modularity and privilege separation. For example, information on an incoming voice call received through Bluetooth or Skype can be propagated and interpreted by any currently running music player, which can react by muting the volume or pausing playback until the call is finished.[3]

Most systems implement a privileged system channel, together with a private channel for each logged-in user, so that available information in the D-Bus registry can be restricted. Accordingly, the D-Bus service includes both a system daemon (for events such as "new hardware device added" or "printer queue changed") and a distinct daemon for each user login session (for general inter-process communication needs between applications started by the particular user). Applications communicate with daemons over Unix domain sockets. The message bus is built on top of a general one-to-one message passing framework, which any two applications can also use to communicate directly and without going through the message bus daemon.[4]

As of January 2014, there is an ongoing development project called kdbus that aims to replace D-Bus with a kernel-mediated peer-to-peer inter-process communication mechanism. Beside performance improvements, kdbus would have advantages arising from already existing Linux kernel features such as namespaces and auditing.[5][6]


Example of usage in Linux-based systems. The dbus-daemon is essentially at the core of the modern Linux graphical desktop environment. Binder is the counterpart used on Android.

D-Bus has three architectural layers:[3]

  • libdbus - a library that allows two applications to connect to each other and exchange messages
  • dbus-daemon - a message-bus daemon executable, built on libdbus, that multiple applications can connect to. The daemon can route messages from one application to zero or more applications, thereby implementing the publish/subscribe paradigm.
  • wrapper libraries based on particular application frameworks

In 2013 the systemd project rewrote libdbus in an effort to simplify the code, but it turned out to significantly increase the performance of D-Bus as well. In preliminary benchmarks, BMW found that the systemd D-Bus library increased performance by 360%.[7]


Messages received over a D-Bus connection get routed to a specific object, not to a process. It thus appears to clients as if they are interacting with an object whether or not there actually is an object on the other side.

D-Bus defines a name for each object which looks like (but is not actually) a POSIX filesystem path, e.g., /org/kde/kspread/sheets/3/cells/4/5. D-Bus objects' names are conventionally namespaced to help with independently developing code modules.[8] Namespaces are generally prefixed with the developer's reserved domain name components (e.g. /org/kde).

See also[edit]


  1. ^ "Announcing D-Bus 1.8.12". 2014-11-24. Retrieved 2014-12-26. 
  2. ^ Havoc's Blog July, 2007
  3. ^ a b Robert Love (2005-01-05). "Get on the D-BUS". Linux Journal. Retrieved 2014-10-14. 
  4. ^ "dbus". freedesktop.org. 2014-01-20. Retrieved 2014-10-14.  |chapter= ignored (help)
  5. ^ Jake Edge (2013-05-30). "ALS: Linux interprocess communication and kdbus". LWN.net. Retrieved 2014-04-11. 
  6. ^ Jonathan Corbet (2014-01-13). "The unveiling of kdbus". LWN.net. Retrieved 2014-04-11. 
  7. ^ "ALS: Linux inter-process communication and kdbus". LWN.net. 2013-05-30. Retrieved 2013-11-13. 
  8. ^ "D-Bus Tutorial". 

External links[edit]