Package Details: kodi-standalone-service 1.112-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: 1.42
First Submitted: 2014-11-05 20:25
Last Updated: 2020-10-21 11:42

Latest Comments

« First ‹ Previous ... 4 5 6 7 8 9 10 11 12 13 14 ... Next › Last »

graysky commented on 2017-03-03 21:06

@red - Yes, on a box that needs the 340xx drivers, I too have to remove the vt7. Dunno if there is a fix in the works or not, see:

redbaron commented on 2017-03-03 19:16

I have same problem as @ricrogz, removing vt7 helped but then shutdown function disappeared from kodi's "power options", changing vt7 to vt1 worked.

graysky commented on 2017-02-21 23:15

Does that series of nvidia cards use the 340xx drivers? Best to continue this in the thread you started[1].


invik commented on 2017-02-21 22:46

@graysky -- sorry, forgot to mention: the card is an Nvidia GT 610. Also, I am not running kodi as root: observe the "-u kodi" after the sudo.

I have been looking around the problem for several days now, and just a few minutes ago I made some progress:

The problem seems to be the "vt7" option at the end of the command line. Somehow, it looks like systemd dislikes it, and, if I lower the number (i.e. vt2 or vt3), or even remove the parameter, the errors in the Xorg log are gone, and kodi starts again (but takes a while to do so, but this seems more related to some issues with pulseaudio, which, despite all my attempts to disable it, still spawns every time I start kodi).

graysky commented on 2017-02-21 22:09

@ric - What hardware? Also, never run kodi as root. It's unsafe and potentially changes the permissions on /var/lib/kodi so that the kodi user cannot write to it and subdirs.

What I can tell you is that after an update a few days ago, my nvidia-340xx machine stopped running as the kodi user via the service. I enabled [testing] and updated and everything works again.

invik commented on 2017-02-21 22:03

I'm unable to start kodi by using the service file from this package, but I still can start it without any problems by issuing (as root):

sudo -u kodi /usr/bin/xinit /usr/bin/kodi-standalone -- :0 -nolisten tcp vt7

I always get this line in my Xorg.0.log file:

[ 31.070] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 11 paused 1
[ 31.070] (EE) Error systemd-logind returned paused fd for drm node

And, after that, the wrong "glx" driver gets loaded (the default one in the xorg package), and kodi dies out in a black screen, spitting out crashlogs in user kodi's home directory.

Does this happen to anyone else? any ideas on how to fix this?

(I'm not claiming this package is broken, just asking for help...)

gsstratton commented on 2017-02-07 21:03

my apologies. Was my config. Did a factory reset and it worked. There was just absolutely nothing in my journalctl or service status. Sorry for shooting from the hip like that.

graysky commented on 2017-02-07 20:08

@gss - Works fine on several different machines. You haven't provided any debugging info to help you.

graysky commented on 2017-02-07 20:08

@gss - Works fine on several different machines. You haven't provided any debugging info to help you.

gsstratton commented on 2017-02-07 19:32

No longer working with v17.0