You are not logged in.
According archwiki notifications should be run with client existing in system immediately as most daemons provide their own service file to Dbus.
So running
notify-send --icon=gtk-info Test "Why do the notifications not work"should produce one in DE's.
In WM's I need standalone notification daemon to do exactly the same. I tried NotifyOSD which I pressume should be launched as notification sends (dbus service file was provided with package), but really nothing happened.
I tried dunst, which is more lightweight and more suited for such situations. I used default config and so, to get it runing. Even tried to link service file provided from package to org.freedesktop.Notifications.service to no avail. I tried to run it sepperatly with startup notifications and got:
Name Lost. Is Another notification daemon running? Notification on startup blinked for a second.
Then I tried to run:
dbus-launch dunst This time it seems I made it run startup notification and dunst process exist. Still nothing happened, when I sent notification.
What information should I check (logs, etc) to see what's wrong?
And what I could do to solve problems with dunst or what other notification daemons should I try? I want to get notifications on i3 working.
Offline