I’ve recently installed i3wm and I’m currently learning how to configure it. I’ve ran into an issue where my screenshot utility, Flameshot, crashes once I take a screen shot. After some reading I’ve discovered that this has to do with dunst.
From Flameshot troubleshooting FAQ:
Most tiling window managers do not come with a notification daemon, and Flameshot communicates with the user through notifications. This means that Flameshot is dependent on a notification manager to be installed and running. Easy way to test if you have a notification manager is to try notify-send "test" in your terminal. If you see the notification, you have it, otherwise we suggest you to install a notification manager such as dunst:
Naturally I’ve got dunst installed as I ran the endeavour i3 install scripts (manually, not through calamares) so that my i3 config file has exec_always --no-startup-id dbus-launch dunst --config ~/.config/dunst/dunstrc in it.
However I’ve noticed that dunst doesn’t seem to work unless I manually run ‘dunst’ in the command line. If I run notify-send test it doesn’t come up before I run dunst in another terminal.
Is this an issue that other people are having as well? And does anyone know of a solution or how to find a solution?
Apparently, dunst wasn’t running at all on my system even though I had exec --no-startup-id dbus-launch dunst --config ~/.config/dunst/dunstrc in my i3 config file, so I just added exec dunst to it and now it works. It’s still not optimal since the notifications are displayed at the bottom of the screen while I have my bar at the top and since I don’t have a ‘click to disable notifications option’ (yet) but it works!
Damn, I love the feeling of figuring something out.
Thanks Joe<3 might not have been the concrete solution, but it made me find out what the issue was<3