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.77
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 8 9 10 ... Next › Last »

ghen commented on 2020-09-14 19:12

I verified with KODI_DATA=/tmp/kodifoo and it fired up a "new"/empty kodi instance. ;-) This allows me to move my kodi installation out of /var/lib/kodi without using symlinks.

graysky commented on 2020-09-14 19:08

@ghen - Have you verified that your proposed modification works? Is the contents of your /etc/default/kodi simply KODI_AE_SINK=ALSA? I would need to read up to verify that the file that the user would edit is working as expected?

ghen commented on 2020-09-14 18:18

Some low-level aspects of Kodi's behaviour (mostly hardware/driver workarounds, but also global paths like KODI_DATA or CRASHLOG_DIR) can be controlled through environment variables, it would be nice if the systemd unit could include an EnvironmentFile to put such settings in, rather than having to override the unit with individual Environment= flags, or worse, editing the /usr/bin/kodi-standalone script as suggested in https://wiki.archlinux.org/index.php/Kodi#Using_ALSA

Just add to each .service file something like:

EnvironmentFile=-/etc/default/kodi

(The leading dash implies the file is not required, so no need to supply a default empty file.)

Not sure if /etc/default/, /etc/conf.d/ or even /etc/sysconfig/ is preferred...

graysky commented on 2020-09-08 15:06

@jimbob - that is a mistake

jimbob commented on 2020-09-08 13:30

The wiki specifically says to use the standalone service if you want to start kodi with an ir remote button press and you can quit/exit Kodi manually, so I don't really follow your argument.

graysky commented on 2020-09-08 13:24

jimbob - The goal of this service is 24/7 standalone. check the wiki for other options. Remember, you are using systemd to start kodi. That is a decision a root level user makes. See my previous comments regarding this.

jimbob commented on 2020-09-08 10:44

I don't want to have Kodi running 24 hours a day. Ideally I would like to start it with a remote control key press and have it automatically exit after an hour or so of inactivity. Thanks.

This reply looks useful.

graysky commented on 2020-09-08 10:34

@jimbob - My bad, yes, I am referring to options under the "Power Options." I only have two under Settings>System>Shutdown functions as well. I am not sure how to modify this without further study.

What is your use case? You want the system (root user) to enable the service via systemctl but you want the unprivileged user (kodi) to be able to stop it dropping back to the TTY/login screen?

jimbob commented on 2020-09-07 22:32

No I only have Shutdown and Suspend. The Kodi wiki says Quit, but Exit, Quit and systemctl stop surely all do the same thing. I was wondering if the missing options were a deliberate design choice for the standalone service so as not to logout leaving the device in a potentially unusable state. Looking at the options you've listed I wonder if you're talking about the general power menu, whereas I am talking about the Power Saving -> Shutdown function menu?

graysky commented on 2020-09-07 21:36

You should have 5 options, exit, power off system, custom shutdown timer, suspend, and reboot. There is not an option to quit. You do that on the terminal via a call to systemctl like any other service.