Package Details: kodi-standalone-service 1.137-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: 68
Popularity: 0.038948
First Submitted: 2014-11-05 20:25 (UTC)
Last Updated: 2024-03-12 11:57 (UTC)

Dependencies (6)

Required by (1)

Sources (1)

Latest Comments

« First ‹ Previous 1 .. 8 9 10 11 12 13 14 15 16 17 18 .. 22 Next › Last »

Hell-G commented on 2017-03-10 22:24 (UTC)

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 (UTC)

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 (UTC)

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

Hell-G commented on 2017-03-10 16:22 (UTC)

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 (UTC)

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 (UTC)

@red - good point!

redbaron commented on 2017-03-04 10:34 (UTC)

Dual monitor is possible but for standalone HTPC it's not usual. And mostly this package is used on systems when KODI is started upon HTPC startup without any additional DE.

graysky commented on 2017-03-04 09:33 (UTC)

@redbaron - This is how it was originally setup by our team.[1] I think vt1 is the default for greeters. I can confirm that lxdm uses it anyway. Is it possible to have a box that drives both TV (HDMI1) and a monitor simultaneously (HDMI2 or DVI or DSUB, etc)? 1. https://git.archlinux.org/svntogit/community.git/commit/trunk?h=packages/xbmc&id=9763c6d32678f3a3f45c195bfae92eee209d504f

redbaron commented on 2017-03-03 21:20 (UTC) (edited on 2017-03-03 21:23 (UTC) by redbaron)

I am using nvidia 378.13-3, but same problem. I think main problem is better described here https://bugs.archlinux.org/task/53090. Why not to use vt1 by default?

graysky commented on 2017-03-03 21:06 (UTC)

@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: https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/nvidia-340xx-utils&id=d342a4bee79a215686d3c431215054b9ce0cc79f

« First ‹ Previous 1 .. 8 9 10 11 12 13 14 15 16 17 18 .. 22 Next › Last »