Restarting bspwm messes up the customized output of dunst at times

[beyond9thousand]

Issue description

Dunst randomly throws incorrect customized outputs after restarting bspwm.

This is what my notifications normally look like

This is what happens when I restart my bspwm (only at random restarts). This continues until I have restarted bspwm a couple of times and then it fixes itself

In the event of the bug mentioned above, this is what the output of systemctl --user status dunst reads

dunst.service - Dunst notification daemon
     Loaded: loaded (/usr/lib/systemd/user/dunst.service; static)
     Active: active (running) since Wed 2022-06-08 17:15:32 IST; 2s ago
       Docs: man:dunst(1)
   Main PID: 107026 (dunst)
      Tasks: 4 (limit: 18997)
     Memory: 3.4M
        CPU: 44ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/dunst.service
             └─107026 /usr/bin/dunst

Jun 08 17:15:32 b9k systemd[80895]: Starting Dunst notification daemon...
Jun 08 17:15:32 b9k systemd[80895]: Started Dunst notification daemon.
Jun 08 17:15:32 b9k dunst[107026]: WARNING: No icon found in path: 'dialog-information'

Additionally output of dunst reads the following WARNING: No icon found in path: 'dialog-information'

Installation info

• Version: Dunst - A customizable and lightweight notification-daemon 1.8.1 (2022-03-02)
• Install type: package
• Window manager: bspwm

Relevant configurations

• bspwmrc: https://github.com/beyond9thousand/dotfiles2.0/blob/master/.config/bspwm/bspwmrc
• dunstrc: https://github.com/beyond9thousand/dotfiles2.0/blob/master/.config/bspwm/dunstrc
• picom.conf: https://github.com/beyond9thousand/dotfiles2.0/blob/master/.config/bspwm/picom.conf

[bynect]

Does this still occur. If so, could you get a debug log for when it happens? Also, have you tried simply restarting the dunst service without bspwm?

[bynect]

This could be due to the fact that dunst is called by a notification before it is started in the xinitrc with the corrent arguments