You are not logged in.
This is a screenshot of my desktop just after login.
On starting ncmpcpp (which calls a script mpdnotify on song change : a script that uses notify-send to inform me about which song is playing and such) this is how the notifications appear :
However, if I start dunst from the terminal, and then run ncmpcpp again, the notifications appear as such (intended configuration) :
I'm only calling dunst from within .xinitrc
Not just ncmpcpp, even `notify-send "sampletext"` shows up weird post login (without executing dunst from terminal).
After login, executing `ps x` shows :
2185 ? SNl 0:00 dunst -config /home/ap/.i3/dunstrcWhile, after executing dunst from terminal, `ps x` shows :
3130 pts/1 SNl 0:00 dunst -config /home/ap/.i3/dunstrcIf I execute dunst from within .i3/config, instead of .xinitrc, then the networkmanager notifications appear weird, but the ncmpcpp ones appear fine.
Could you point me in the right direction as to how to go about fixing it?
Here are the relevant configs :
.xinitrc : https://raw.githubusercontent.com/chrzr … x/.xinitrc
.i3config : https://raw.githubusercontent.com/chrzr … i3/dunstrc
EDIT : Anyhow, it seems I've fixed the issue by executing dunst from within .xinitrc as well as .i3/config. Now, all notifications look fine. I, however, now have 2 instances of dunst running (both with the same config).
3863 ? Sl 0:00 dunst -config /home/ap/.i3/dunstrc
3899 ? Sl 0:00 dunst -config /home/ap/.i3/dunstrcCould someone shed some light on this issue, and how I may go about rectifying it?
EDIT 2 : The solution lies in not starting i3 with dbus. The relevant change to .xinitrc is basically to call just
exec i3in place of
exec dbus-launch --exit-with-session i3And now, we can stop executing dunst from within i3. ![]()
Thank you for taking the time to read this. ![]()
Last edited by ablip (2016-04-11 06:19:26)
Offline
Read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_code
Offline
I'm sorry about that. The pictures were under 50kb, and the check on the dimensions of the image escaped my mind. Anyhow, it seems I've fixed the issue by executing dunst from within .xinitrc as well as .i3/config. Now, all notifications look fine. I, however, now have 2 instances of dunst runnig (both with the same config).
Could someone shed some light on this issue, and how I may go about rectifying it?
Offline