Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
dbus [2025/03/23 12:55] – tmaier | dbus [2025/03/23 14:21] (current) – tmaier | ||
---|---|---|---|
Line 12: | Line 12: | ||
===== DBUS Implementations ===== | ===== DBUS Implementations ===== | ||
- | - GDBus (Gnome) | + | * GDBus (Gnome) |
- | - QT/KDE D-Bus | + | |
- | - dbus-broker (Arch) | + | |
==== dbus-broker ==== | ==== dbus-broker ==== | ||
Source: [[https:// | Source: [[https:// | ||
+ | |||
+ | * Each dbus-broker instance provides a message bus | ||
+ | * Each dbus-broker instance gets started by a parent process (// | ||
+ | * dbus-broker only implements message mediation (bus setup and external communication needs to be handled by the // | ||
+ | * The // | ||
+ | * The unix socket is used by dbus-broker to accept commands from the // | ||
+ | * Example commands issued by the Controller: Create listener sockets, specify bus policy, create activatable names, react to bus events. | ||
+ | |||
+ | dbus-broker-launch: | ||
+ | * dbus-broker-launch spawns and manages one message bus | ||
+ | * Configuration file is specified via '' | ||
+ | * '' | ||
+ | |||
+ | === dbus-broker on Arch Linux === | ||
+ | Source: [[https:// | ||
+ | |||
+ | During systemd installation, | ||
+ | |||
+ | Alternatively to dbus-broker, | ||
===== Desktop Notifications ===== | ===== Desktop Notifications ===== | ||
Line 29: | Line 48: | ||
Daemons: | Daemons: | ||
- | * dunst | + | * dunst: Lightweight, |
- | * NotifyOSD / notify-osd | + | * NotifyOSD / notify-osd: Configurable, |
Depending on the Desktop Environment, | Depending on the Desktop Environment, | ||
Typically, DBUS service files are shipped with notification daemons, e.g., ''/ | Typically, DBUS service files are shipped with notification daemons, e.g., ''/ | ||
+ | |||
+ | ==== Troubleshooting ==== | ||
+ | Tools: | ||
+ | * Bustle: Recording D-Bus communication, | ||
+ | * D-Spy: Inspect buses/ | ||