34515c3338
If I call systemctl to shutdown or reboot, the effect is that it does not honor kodi-x11.service's ExecStop= line which results in an unclean exit of kodi and of data loss since kodi writes out some data when it exits. By contrast, calling systemctl to stop the service works as expected. It seems systemd treats processes in user.slice differently that those in system.slice and that removing PAMName=login was to blame for kodi's processes running in user.slice. Discussion: https://lists.freedesktop.org/archives/systemd-devel/2020-December/045713.html https://bbs.archlinux.org/viewtopic.php?id=261684
21 lines
612 B
Desktop File
21 lines
612 B
Desktop File
[Unit]
|
|
Description=Kodi standalone (Wayland)
|
|
After=remote-fs.target 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
|
|
EnvironmentFile=-/etc/conf.d/kodi-standalone
|
|
TTYPath=/dev/tty1
|
|
Environment=WINDOWING=wayland
|
|
ExecStart=/usr/bin/cage -- /usr/bin/kodi-standalone
|
|
ExecStop=/usr/bin/killall --user kodi --exact --wait kodi-wayland
|
|
Restart=on-abort
|
|
StandardInput=tty
|
|
StandardOutput=journal
|
|
|
|
[Install]
|
|
Alias=display-manager.service
|