What Is D-Bus Message Bus Daemon? Is It Safe to Disable at Startup?
dbus-daemon is the D-Bus message bus service used by Linux apps and desktop components. It is normally safe and should usually stay enabled.
- Verdict
- Keep runningdbus-daemon is a core Linux IPC service used by desktop sessions, system services and many apps, so disabling it can break normal system behavior.
- File name
- dbus-daemon
- Publisher
- freedesktop.org
- Platforms
- Linux
- Reviewed
What Is dbus-daemon?
dbus-daemon is the background service behind D-Bus, a standard Linux message bus used for inter-process communication. In plain English, it lets apps and system components talk to each other safely.
On Linux, there are usually two kinds of D-Bus buses:
- a system bus for system services
- a session bus for your desktop session and user apps
Many common features depend on it: desktop notifications, power management, audio controls, network status, file manager integration, portal services, and app-to-app requests. On many systems it starts automatically as part of the desktop session or system startup.
Is It Safe?
Yes — the real dbus-daemon from freedesktop.org is a normal and trusted Linux system component.
It is not usually malware, and on a standard Linux desktop it is expected to be running. That said, anything can be impersonated. If you are unsure, check the process path with a command such as ps, top, htop, or systemctl status dbus. On many distributions the binary is in a standard system location such as /usr/bin/dbus-daemon, but the exact path can vary by distro.
If you find a process named dbus-daemon running from a user-writable folder, a temporary directory, or inside a suspicious app bundle, investigate it. Also check which package owns the file using your distro's package manager if needed.
Should I Disable It at Startup?
No, in most cases you should keep it enabled.
dbus-daemon is not a typical optional tray app or updater. It is part of the plumbing that many Linux desktops and services rely on. Disabling it can cause login session problems, missing notifications, broken settings panels, app launch failures, or other odd behavior.
If you are looking to reduce startup load, target optional user apps instead of D-Bus itself. On Linux, dbus-daemon is generally a dependency, not clutter.
Why Is It Using High CPU or Memory?
dbus-daemon usually uses very little CPU and memory. If usage is high, the problem is often another app flooding the bus rather than D-Bus itself being the root cause.
Common causes include:
- a buggy desktop extension or panel app
- a misbehaving background service
- repeated notification or portal requests
- an app stuck in a crash/restart loop
If CPU use stays high, look for what started at the same time and what other processes are active. Logging out and back in may clear a broken session bus state. A reboot can help too, but if the issue returns, focus on recently installed apps, desktop extensions, or services.
Do not kill or remove D-Bus as a first fix on a normal desktop system.
How to Disable or Remove It
Usually, you should not disable or remove dbus-daemon.
If it appears in a custom startup entry, container, or app-specific launcher, verify what that entry actually starts. On most Linux systems, D-Bus is managed by the OS, init system, or desktop session rather than a simple XDG autostart item.
If you are troubleshooting, disable the app or service causing the bus traffic instead of D-Bus itself. Removing the D-Bus package can break desktop features and dependencies.
Where Kudu Helps
Kudu can help you find the real startup item that is causing trouble around dbus-daemon.
- Performance Monitor shows which processes are actually using CPU and memory right now.
- Startup Manager lets you review Linux XDG autostart entries and disable optional apps that load with your session.
- Malware Scanner can help check for suspicious persistence or a fake process using a trusted name.
- System Cleaner can clear supported app caches if a buggy app is misbehaving, without touching important system components.
If dbus-daemon is busy, use Kudu to trace the noisy app around it — not to remove a core Linux service.
Frequently asked questions
- Can I end dbus-daemon to stop high CPU use?
- You can, but it is usually a bad first step on a desktop Linux system. The better fix is to find the app or service causing the D-Bus traffic.
- Is dbus-daemon the same as malware?
- Normally no. The legitimate process is a standard Linux component, but a fake process using the same name should be investigated by checking its file path and owning package.
- Why are there multiple D-Bus related processes?
- Linux can use separate system and session buses, and some environments also use related helpers. That can be normal depending on your distro and desktop setup.
See every app that starts with your computer
Kudu’s Startup Manager lists Run keys, Startup folder entries, scheduled tasks, Launch Agents, and XDG autostart items in one place. On Windows it also shows each item’s boot time impact.
Download Kudu Free →