Package Details: kodi-standalone-service 1.93-1

Git Clone URL: https://aur.archlinux.org/kodi-standalone-service.git (read-only)
Package Base: kodi-standalone-service
Description: Systemd service to run kodi in stand-alone mode without a DE
Upstream URL: https://github.com/graysky2/kodi-standalone-service
Licenses: GPL
Replaces: xbmc-standalone-service
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 51
Popularity: 0.499415
First Submitted: 2014-11-05 20:25
Last Updated: 2017-08-09 16:33

Latest Comments

kuch3n commented on 2017-04-09 08:05

fails to start :(
09:47:13.744 T:140299952466048 ERROR: CWinSystemX11::XErrorHandler: BadValue (integer parameter out of range for operation), type:0, serial:91, error_code:2, request_code:155 minor_code:3
09:47:13.744 T:140299952466048 ERROR: GLX Error: Could not create context

graysky commented on 2017-03-11 09:49

@Hell-G - That's fine. I was mistaken, it's not display.service, it's display-manager.service which should be a symlink to whatever you're using, gdm in your case, lxdm in mine:

ls -lh /etc/systemd/system/display-manager.service
lrwxrwxrwx 1 root root 36 May 11 2016 /etc/systemd/system/display-manager.service -> /usr/lib/systemd/system/lxdm.service

In any case, yeah, if you want to use the box for things other than kodi, this is probably not for you.

Hell-G commented on 2017-03-11 08:49

Thank you graysky for all the work you have put in and for all your replies here and in the forums! I do not have a display.service, I can only find gdm.service on my system.
Reading your last sentence, I think that "kodi-standalone-service" is not the right thing for me after all. I still want to be able to login as a different user and therefore, getting rid of my display manager is not what I want. I am sorry, that I did not understand this earlier and bothered you here.

graysky commented on 2017-03-10 22:33

@Hell-G - disable display.service (should be symlinked to gdm on your system) and enable kodi.service. "kodi-standalone-service" is for systems that want to use the GUI exclusively for kodi.

Hell-G commented on 2017-03-10 22:24

Thank you for your replies!

1)$ id kodi
uid=420(kodi) gid=420(kodi) groups=420(kodi),90(network),91(video),92(audio),93(optical)

2)$ grep kodi /etc/passwd
kodi:x:420:420:kodi user:/var/lib/kodi:/usr/bin/nologin

3) It has never happened, that my computer booted directly into Kodi. Very interesting. I did not install GDM nor Gnome for Kodi, I use those for when I am doing other stuff than using Kodi.
The service is started and enabled, so I don't see what I am doing wrong. Is GDM and Gnome in the way of kodi-standalone?
$ sudo systemctl status kodi
● kodi.service - Starts instance of Kodi using xinit
Loaded: loaded (/usr/lib/systemd/system/kodi.service; enabled; vendor preset: disable
Active: active (running) since Thu 2017-03-09 21:36:14 CET; 1 day 1h ago
Main PID: 10557 ((xinit))
Tasks: 1 (limit: 4915)
CGroup: /system.slice/kodi.service
└─10557 (xinit)

Mar 09 21:36:14 hostname systemd[1]: Started Starts instance of Kodi using xinit.

Thanks again!

redbaron commented on 2017-03-10 19:38

This package is for booting (not logging) directly into Kodi. You don't need GDM or Gnome, just X, all the dependencies are listed in this package.

graysky commented on 2017-03-10 19:35

What is the output of:
1) id kodi
2) grep kodi /etc/passwd

Hell-G commented on 2017-03-10 16:22

Sorry guys, I have a very basic question. Although I installed kodi-standalone-service a long time ago and I think I was using its functionality, now I am not sure anymore, if I really understand it. What is the main purpose of this package?
My interpretation was, that it offers the possibility to run Kodi without loading a DE. I am using GDM and Gnome and in the past, I had the Kodi user listed on my login screen and I set up passwordless login for it (sorry, I don't remember how I actually did it). So as soon as I select this user, I go directly into Kodi.

Since the last time I updated my system, the Kodi user is no longer shown. So I started digging. The Arch Wiki says: "Note: kodi-standalone-serviceAUR creates a user named kodi, which is not permitted to login, thus autologin will fail with this user." So if the user is not permitted to login, how is it possible, that I used to be able to login in GDM and have Kodi started right away?
Looking at the UID of the Kodi user (420), it makes sense now, that the user is not listed at the login screen, because the ID is <1000. So it is a system user and not supposed to login. But why did it show it for me before?

Or is the package meant to directly boot into Kodi without any further user interaction? But if this is the case, this has never worked for me and I would not know what to adapt to make this work.

I basically just want to be able to go directly into Kodi from the login screen (preferably without password) and don't have a full blown DE running in the background.

Thank you for your help!

graysky commented on 2017-03-04 14:19

Bump to v1.90-1
Changelog: Run on vt1 not vt7 for increased compatibility.
Commit: https://github.com/graysky2/kodi-standalone-service/compare/v1.82...v1.90

graysky commented on 2017-03-04 14:17

@red - good point!

All comments