This package comes with a systemd
unit file that is not supported by the upstream. To enable the unit, run $ systemctl --user enable kanshi.service
. Some notes:
- This unit won't automatically start unless
graphical-session.target
has already started. Though on many users' systems,graphical-session.target
always starts under Sway, Sway actually does not activategraphical-session.target
by default. Thegraphical-session.target
may be activated silently by some other applications/units or by explicitexec
command in the Sway config. - Many other X11 window managers or Wayland compositors also activate
graphical-session.target
. This says, if you sometimes use other WM, likegnome
orkde
,kanshi.service
will also automatically start (and then fail because kanshi is a Sway-only application).
The best practice is to create your own sway-session.target
, and modify (or create your own) the kanshi.service
to be wanted by sway-session.target
. See the Wiki at Sway's GitHub and also ArchWiki:
Pinned Comments
pychuang commented on 2021-02-24 18:58
This package comes with a
systemd
unit file that is not supported by the upstream. To enable the unit, run$ systemctl --user enable kanshi.service
. Some notes:graphical-session.target
has already started. Though on many users' systems,graphical-session.target
always starts under Sway, Sway actually does not activategraphical-session.target
by default. Thegraphical-session.target
may be activated silently by some other applications/units or by explicitexec
command in the Sway config.graphical-session.target
. This says, if you sometimes use other WM, likegnome
orkde
,kanshi.service
will also automatically start (and then fail because kanshi is a Sway-only application).The best practice is to create your own
sway-session.target
, and modify (or create your own) thekanshi.service
to be wanted bysway-session.target
. See the Wiki at Sway's GitHub and also ArchWiki: