The mystery of what is starting dunst

This seems like a dumb question, but I absolutely can’t seem to figure it out.

I have no idea what is starting dunst. It doesn’t seem to be anywhere in any initialization, yet it mysteriously starts.

It’s not in my i3 config.

I cannot find it as a systemd service (it doesn’t have some weird name does it?).

I’m using lightdm, it’s not started in /etc/lightdm/Xsession and does not appear to be started by any of the scripts that are run by that.

It’s not in my .xinitrc.

Any ideas what might be starting it?

This is mostly just to understand the boot process, I actually want it running, at least for now.

Note: It may seem like there is no need to manually start dunst, as it may get autostarted by dbus-daemon when programs send notifications through D-Bus. However, the notification service frequently has multiple daemons installed, and there is no way to know which daemon will be autostarted. The dbus-daemon maintainers explicitly warn against relying on autostart for multiple-provider services.

1 Like

Wow, can’t believe I missed that :man_facepalming:


1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.