Open denisok opened 4 years ago
According to https://github.com/emersion/mako#running, mako
does not need to be started manually (it is dbus activated) unless multiple notification daemons are installed.
hm, thanks. Have you tested it ? @agraul
I have exec mako
in the conf now.
I also had exec mako
in my conf, but I just ran killall mako && ps aux | grep mako; notify-send "test"
and saw a notification - no mako process was visible in the ps aux
aha, good to know ) you can submit PR removing that ) Or I will do it occasionally later.
killall mako && ps aux | grep mako; notify-send "test"
Hmm, doesn't work for me. WIthout running mako
I don't get anything. And yes, dbus seems to be running and /usr/share/dbus-1/services/fr.emersion.mako.service
is installed:
~@kusansky$ pgrep -f -a dbus
4912 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
5615 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
5694 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3
~@kusansky$
Just to note, there is https://github.com/alebastr/sway-systemd by @alebastr (for Fedora, I guess), which may be something interesting.
one of the advantages of systemd for the waybar - is crash.
Currently experiencing waybar crash and that makes me just start it manually. With systemd it would be less noticeable and destructive for me I think.
add systemd service to: