Open beyond9thousand opened 2 years ago
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?
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
Issue description
Dunst randomly throws incorrect customized outputs after restarting bspwm.
This is what my notifications normally look like![image](https://user-images.githubusercontent.com/77363063/172603361-632139e4-80dc-4d2f-84f1-bcf31c778452.png)
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![image](https://user-images.githubusercontent.com/77363063/172603835-66d6f56c-4900-45a5-90b8-8737fd9f4278.png)
In the event of the bug mentioned above, this is what the output of
systemctl --user status dunst
readsAdditionally output of
dunst
reads the followingWARNING: No icon found in path: 'dialog-information'
Installation info
Dunst - A customizable and lightweight notification-daemon 1.8.1 (2022-03-02)
package
bspwm
Relevant configurations