Package Details: kodi-standalone-service 1.132-3

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.73
First Submitted: 2014-11-05 20:25
Last Updated: 2021-07-20 12:10

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 ... Next › Last »

gkun commented on 2021-05-09 10:18

Did anyone run into update issues with the newest version? For me it will not pass the b2sums validity check:

==> Validating source files with b2sums... kodi-standalone-service-v1.129.tar.gz ... FAILED ==> ERROR: One or more files did not pass the validity check! error downloading sources: kodi-standalone-service

khvalera commented on 2021-03-22 16:54

@graysky - I already saw that the kodi-rpi package was compiled in armlinux, it already has files, a conflict occurs.

graysky commented on 2021-03-21 22:22

I added it since some users built on Arch ARM and caused them problems. Are you experiencing an issue with it?

ghen commented on 2021-03-21 21:09

That's not really relevant. It doesn't make sense to "build" separate i686, x86_64, and soon maybe x86_64-v3 versions of this non-binary package.

graysky commented on 2021-03-21 20:58

why is the architecture x86_64 specified and notany? @khvalera - Arch ARM ships the needed files in the respective packages.

khvalera commented on 2021-03-21 20:23

why is the architecture x86_64 specified and notany?

francoism90 commented on 2021-03-02 07:50

Do you guys run kodi-wayland or kodi-x11 as standalone? I'm thinking of moving to Wayland as standalone.

graysky commented on 2020-12-14 20:37

@ghen - the issue we are running into here is complex for kodi-x11 due to systemd and/or my lack of mastery of all its myriad nuances. For one, we are starting xorg-server and then starting kodi within in one step which led to a bit of confusion and discussion to get it to both start and stop properly[1,2].

Beyond that, differences in systemctl stop kodi-x11 and systemctl reboot caused me to make the most recent change removing the PAMName= so I could get the entire thing under the system.slice and out of the user.slice[3].

I am open to suggestions to limit the kodi user to just the physical keyboard.


ghen commented on 2020-12-14 20:19

Thanks. Not sure it's a good idea to give kodi unrestricted access to all input devices though? (even if the user switches to another tty?)

graysky commented on 2020-12-14 19:58

@ghen - I think kodi may need to be in the input group now that the PAMName= directive is removed. EDIT: yep, I will fix and update. Thank you for the report.