search

emersion / mako

A lightweight Wayland notification daemon
https://wayland.emersion.fr/mako
MIT License
2.18k stars 139 forks source link

Mako failing WAYLAND_DISPLAY condition check, but WAYLAND_DISPLAY is set #427

Closed cmvanb closed 2 years ago

cmvanb commented 2 years ago

Previously mako has worked fine with sway. Now that I've installed a different wayland compositor, riverwm, mako is failing a condition check. I don't understand why it's failing, because when I check printenv I see WAYLAND_DISPLAY=wayland-1.

Can anyone help me understand where it's going wrong?

Here are the relevant lines from journalctl:

May 27 15:04:41 workstation dbus-daemon[759]: [session uid=1000 pid=759] Activating via systemd: service name='org.freedesktop.Notifications' unit='mako.service' requested by ':1.3442' (uid=1000 pid=14503 comm="busctl -j --user call org.freedesktop.Notification")
May 27 15:04:41 workstation systemd[685]: Lightweight Wayland notification daemon was skipped because of a failed condition check (ConditionEnvironment=WAYLAND_DISPLAY).
May 27 15:06:41 workstation dbus-daemon[759]: [session uid=1000 pid=759] Failed to activate service 'org.freedesktop.Notifications': timed out (service_start_timeout=120000ms)
emersion commented 2 years ago

You need to import the WAYLAND_DISPLAY var into systemd.