Package Details: kodi-standalone-service 1.135-1

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: 65
Popularity: 0.60
First Submitted: 2014-11-05 20:25
Last Updated: 2022-01-18 12:27

graysky commented on 2015-03-13 21:38

@bjo - It's a systemd solution... you need to start/stop the service, not the application.

bjo commented on 2015-03-13 21:36

The service doesn't work here any more. Running kodi manually as kodi results in

/usr/lib/xorg-server/Xorg.wrap: Only console users are allowed to run the X server

Putting "allowed_users=anybody" in Xwrapper.config leads to "no permission" on vt7

graysky commented on 2015-02-19 20:06

I will change the arch=any to arch=('x86_64' 'i686') to prevent this from ARM users.

graysky commented on 2015-02-19 20:05

I will add a conflicts=kodi-rbp line to the PKGBUILD but not bump the pkgver.

thealchemist commented on 2015-02-19 10:56

Sorry for removing the latest comment, yeah I will go for it :)

thealchemist commented on 2015-02-19 10:54

Ok, now I got it (after comparing both packages "kodi" and "kodi-rbp"myself). And it is not as easy as I hoped in the beginning.

So some more testing leads to:
- the kodi packages do the same things (concerning no user creation) during install on x86 and ARM and look to be compatible with the package.
- on my Rasberry Pi kodi + kodi-standalone-package do not work out of the box (failed with systemd). Did not test on x86.
- kodi-rbp works flawless on the RBP
- kodi and kodi-rbp both do not depend on xorg-server
- installing kodi-standalone-service package above kodi-rbp is possible after removing its integrated kodi.service (it recognizes kodi-rbp as kodi for some reason)
- installing it on top of kodi-rbp messes the installation (as said before).
- the package does not install if the makepkg file contains "conflicts=('kodi-rbp')"

Ok, i think I have learned my lesson, but I think it should be
Arch x86 != Arch ARM
Arch x86 package == Arch ARM package (roughly, concerning compatibility)
kodi-rbp != kodi (!)

graysky commented on 2015-02-19 10:42

Yes, you understand correctly. Also, it's a wiki, go for it.

thealchemist commented on 2015-02-19 09:36

So Arch ARM creates a user while Arch x86 does not? Then I see that it is getting complicated/incompatible now and its not documented.

This is in contrast to the packages I installed and configured for now (using the Wiki). As far as I know that the Wiki officially only supports x86, but if most packages were essentially compatible, and the Arch ARM developers also link to the Wiki, then there should be an update to the Wiki.

graysky commented on 2015-02-18 20:37

Arch != Arch ARM. Arch ARM ships their kodi package with, in effect, this already mixed in. Best advice is not use AUR packages on Arch ARCH without understanding if they are supplying similar functionality or identical files.

thealchemist commented on 2015-02-18 15:51

@graysky:
I can confirm this, kodi.service works flawless without kodi-standalone-service but I did not get it running with the package. I'm completely new to kodi (only did some research and testing yesterday), but I at the time of writing I cannot find the advantages of this package. I found it as solution in the Wiki.

I believe it was needed with previous xbmc but my current kodi-rbp installation (Rasberry Pi 2) works out of the box if I enable kodi.service in systemd.
On the other hand I was not able to install this package without messing in my setup manually (removing /usr/lib/systemd/system/kodi.service and setting suid mount option in /var).

While installing kodi a user and group named kodi were added (ID 997:997)
After installing kodi-standalone-service kodi.service was broken (kodi ID 997:420) and login group was kodi (420)

I also do not understand in which way the package is different to the current out of the box behaviour (and maybe outperforms it). But honestly for me it looked like its messing my fresh kodi installations rendering it unusable.

Now I do not want to correct the Wiki entry of Kodi, because of my very limited knowledge and because I really respect your work, but I think the Wiki is misleading.

I am willing to do some more testing if it is needed.