How D-Bus supports IPC and its ways of communicating
Filed under Nvidia
Free read 1 of 3A message bus system: a daemon (dbus-daemon or broker) routes messages between clients connected over Unix sockets. Services own well-known names such as org.example.Service and expose objects at paths with interfaces.
The question
Explain how D-Bus supports IPC and the different ways it lets processes communicate (method calls, signals, properties, buses).
Approach
A message bus system: a daemon (dbus-daemon or broker) routes messages between clients connected over Unix sockets. Services own well-known names such as org.example.Service and expose objects at paths with interfaces.
Method calls (request and reply, optionally asynchronous), signals (one-to-many broadcast notifications that clients subscribe to with match rules), properties (get/set/changed via the Properties interface) and error replies.
The system bus serves system services and the session bus serves a user login. A destination is bus name plus object path plus interface plus member. Introspection reveals the API.
Access is governed by policy files; messages are typed and marshalled; calls can time out. Libraries include libdbus, GDBus, sd-bus and Qt D-Bus. Direct peer-to-peer connections also exist.
Tips
- What they are testing: Concrete knowledge of the D-Bus model beyond saying it is IPC; follow-ups usually probe addressing and message types.
- Common mistake: Mixing up method calls (request/reply) and signals (broadcast), or ignoring the session versus system bus distinction.
Related Nvidia questions
Collected from public candidate posts and coding forums. Updated Nov 2026.