Package Details: kodi-standalone-service 1.132-3

Git Clone URL: https://aur.archlinux.org/kodi-standalone-service.git (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: https://github.com/graysky2/kodi-standalone-service
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.68
First Submitted: 2014-11-05 20:25
Last Updated: 2021-07-20 12:10

Latest Comments

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

graysky commented on 2021-08-15 18:20

@wooptoo - Are you using the latest version? This was fixed weeks ago: https://github.com/graysky2/kodi-standalone-service/commit/33dc37310fea769e5eedbc2615850c93961b44e1

Also, the ExecStop is needed or else kodi does not exit cleanly/you lose data. See commit msg: https://github.com/graysky2/kodi-standalone-service/commit/34515c33387381c996c1760619d8554628910321

wooptoo commented on 2021-08-15 15:32

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 https://gist.github.com/radupotop/5ed69a4fc0a06c9341a2cabd82639ee8

francoism90 commented on 2021-08-04 13:05

@graysky Turns out I'm an idiot.. changing the target (https://wiki.archlinux.org/title/Systemd#Targets) to graphical.target fixed the issue. :)

graysky commented on 2021-07-19 14:12

Fixed in 1.132-2, thanks.

ghen commented on 2021-07-19 14:10

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

@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

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

@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: https://wiki.archlinux.org/title/Fscrypt#PAM_module

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

Many thanks. :)

gkun commented on 2021-05-09 23:14

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

graysky commented on 2021-05-09 12:08

@gkun - The checksum works for me. If you're caching your source somewhere manually delete it and try again?