retroarch-standalone-service/x86/init/kodi-wayland.service

[Unit]
Description=Kodi standalone (Wayland)
After=remote-fs.target systemd-user-sessions.service network-online.target nss-lookup.target sound.target bluetooth.target polkit.service upower.service mysqld.service
Wants=network-online.target polkit.service upower.service
Conflicts=getty@tty1.service

[Service]
User=kodi
Group=kodi
RuntimeDirectory=kodi
Environment="XDG_RUNTIME_DIR=%t/kodi"
EnvironmentFile=-/etc/conf.d/kodi-standalone
PAMName=login
TTYPath=/dev/tty1
ExecStart=/usr/bin/cage -- /usr/bin/kodi-standalone
ExecStop=/usr/bin/killall --user kodi --exact --wait kodi.bin
Restart=on-abort
StandardInput=tty
StandardOutput=journal

[Install]
Alias=display-manager.service
Add kodi-wayland.service This allows running Kodi in a Wayland session using the Cage compositor. 2020-05-14 11:19:11 +03:00			`[Unit]`
			`Description=Kodi standalone (Wayland)`
Revert "Consistent behavior on a systemctl stop vs reboot" This reverts commit 34515c33387381c996c1760619d8554628910321. 2021-01-03 08:25:34 -05:00			`After=remote-fs.target systemd-user-sessions.service network-online.target nss-lookup.target sound.target bluetooth.target polkit.service upower.service mysqld.service`
Add kodi-wayland.service This allows running Kodi in a Wayland session using the Cage compositor. 2020-05-14 11:19:11 +03:00			`Wants=network-online.target polkit.service upower.service`
			`Conflicts=getty@tty1.service`

			`[Service]`
			`User=kodi`
			`Group=kodi`
kodi-wayland: use runtime directory created by systemd This will sort out the permissions warning mentionned in #27. The RuntimeDirectory is created in /run/kodi with the necessary permissions, %t points at /run. See systemd.exec(5) and systemd.unit(5). 2020-12-29 01:51:08 +00:00			`RuntimeDirectory=kodi`
			`Environment="XDG_RUNTIME_DIR=%t/kodi"`
support passing environment vars to service 2020-09-14 15:32:22 -04:00			`EnvironmentFile=-/etc/conf.d/kodi-standalone`
Revert "Consistent behavior on a systemctl stop vs reboot" This reverts commit 34515c33387381c996c1760619d8554628910321. 2021-01-03 08:25:34 -05:00			`PAMName=login`
Add kodi-wayland.service This allows running Kodi in a Wayland session using the Cage compositor. 2020-05-14 11:19:11 +03:00			`TTYPath=/dev/tty1`
restore call to kodi-standalone, fixes #26 Calling the kodi-xxx target in ExecStart= was not actually the key to fixing the shutdown bugs in 847b6ec65. Adding the ExecStop= calling killall to the exact target was needed. This commit restores the call to kodi-standalone to allow the "RestartApp" built in to work again and adds the key ExecStop= with killall. 2020-11-08 06:10:38 -05:00			`ExecStart=/usr/bin/cage -- /usr/bin/kodi-standalone`
x86_64: update for kodi.bin[1] 1. https://github.com/archlinux/svntogit-community/commit/50afcc355a5ff3be2fb43faff5c7e690420a3b8c#diff-3e341d2d9c67be01819b25b25d5e53ea3cdf3a38d28846cda85a195eb9b7203a 2021-07-13 17:40:05 -04:00			`ExecStop=/usr/bin/killall --user kodi --exact --wait kodi.bin`
Add kodi-wayland.service This allows running Kodi in a Wayland session using the Cage compositor. 2020-05-14 11:19:11 +03:00			`Restart=on-abort`
			`StandardInput=tty`
better ExecStop to cleanly exit fixes #23 and #24 Direct call to kodi-xxx in ExecStart= allows direction of kill signal to that rather than to kodi-standalone wrapper. This allows the kill signal to hit the indented executable. As well, using killall in the ExecStop= allows for synchronous stopping and for kodi to do shutdown housekeeping tasks such as saving settings, stopping services (web, zeroconf, etc.) and unloading things. 2020-10-10 09:13:36 -04:00			`StandardOutput=journal`
Add kodi-wayland.service This allows running Kodi in a Wayland session using the Cage compositor. 2020-05-14 11:19:11 +03:00
			`[Install]`
use alias to dm.service rather than target fixes #19 Also see: https://bbs.archlinux.org/viewtopic.php?pid=1131267 2020-07-13 12:57:53 -04:00			`Alias=display-manager.service`