You are not logged in.
After installing dunst 1.2.0 and rebooting, I get the following messages out of journalctl after logging in:
systemd[832]: Failed to start Dunst notification daemon.
login[551]: pam_systemd(login:session): Failed to create session: Connection timed outI think what is happening is that systemd is starting graphical-session.target (which dunst.service is PartOf) before X is started. I start X by calling startx in my ~/.bash_profile.
What do I need to modify in order to make dunst.service not crash the login session? For now, I've masked the service and start it manually after X starts.
Offline
I doubt that merely installing dunst lead to this. What else did you do (probably autostart it in some way?) and notably: *how*?
Offline
Thanks, I figured it out.
Deep in my config files, I had a call to notify-send that was called before X started. Moving this to after X starts solved this issue.
Offline