Package Details: kodi-standalone-service 1.136-1

Git Clone URL: (read-only, click to copy)
Package Base: kodi-standalone-service
Description: Systemd services to run kodi in stand-alone mode without a DE
Upstream URL:
Licenses: MIT
Replaces: kodi-standalone-gbm-service, kodi-standalone-wayland-service, kodi-standalone-x11-service
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 64
Popularity: 0.36
First Submitted: 2014-11-05 20:25 (UTC)
Last Updated: 2022-07-04 19:58 (UTC)

Latest Comments

1 2 3 4 5 6 .. 20 Next › Last »

graysky commented on 2021-08-15 18:20 (UTC) (edited on 2021-08-16 11:33 (UTC) by graysky)

@wooptoo - Are you using the latest version? This was fixed weeks ago:

Also, the ExecStop is needed or else kodi does not exit cleanly/you lose data. See commit msg:

wooptoo commented on 2021-08-15 15:32 (UTC) (edited on 2021-08-15 15:34 (UTC) by wooptoo)

The kodi-x11.service now fails since it can't find the kodi-x11 binary. Replacing the ExecStart directive with the following fixed it:

ExecStart=/usr/bin/xinit /usr/bin/kodi --standalone -fs -- :0 -quiet -nolisten tcp vt1

Also the ExecStop line is not necessary since systemd kills all processed owned by the kodi user.

Complete file here

francoism90 commented on 2021-08-04 13:05 (UTC)

@graysky Turns out I'm an idiot.. changing the target ( to fixed the issue. :)

graysky commented on 2021-07-19 14:12 (UTC)

Fixed in 1.132-2, thanks.

ghen commented on 2021-07-19 14:10 (UTC)

kodi-standalone-service-v1.132.tar.gz ... FAILED ==> ERROR: One or more files did not pass the validity check!

The current download file has a different checksum: b2sums=('29b0ace7b1519f25cf616f6c7aab2534aee2b3af92e702bb4bcaca054d4a1bb606b27c6a030edc6006b05464350eb67ad29de2693a088d0aac4881049e0c33a7')

francoism90 commented on 2021-07-17 08:24 (UTC)

@graysky Thanks for your reply. :)

I don't know to be honest, will try to find out.

Maybe it's not fscrypt, the only other thing I could think about is apparmor. I have enabled logging in Kodi, will report back if this shows something useful.

graysky commented on 2021-07-15 17:55 (UTC)

I have no experience with fscrypt. Does the service need to add something in the After= to capture your decrypted stuff?

francoism90 commented on 2021-07-14 06:46 (UTC)

@graysky When starting kodi-*.service (any variant), it mostly doesn't start for me - it also doesn't work on boot. It seems to be caused by fscrypt (ext4), starting kodi manually works, however it simple freezes.

I have done changes to the PAM modules:

Could this be the cause? Other things I could try?

Many thanks. :)

gkun commented on 2021-05-09 23:14 (UTC)

@graysky Thank you! I cleared yay's cache and everything worked.