Package Details: kodi-standalone-service 1.137-2

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.27
First Submitted: 2014-11-05 20:25 (UTC)
Last Updated: 2024-07-06 08:38 (UTC)

Dependencies (6)

Required by (1)

Sources (1)

Latest Comments

« First ‹ Previous 1 .. 11 12 13 14 15 16 17 18 19 20 21 22 Next › Last »

graysky commented on 2016-09-11 01:25 (UTC)

@zofiel - I am not an expert, but removing it seems to have no ill-effects and solves problems for others.

zofiel commented on 2016-09-10 09:09 (UTC)

so usr/bin/dbus-launch --exit-with-session si no longer necessary? To modify the kodi wiki.

graysky commented on 2016-09-08 19:49 (UTC)

Bump to v1.81-1 Changelog: Increased compatibility with new dbus package. Commit: https://github.com/graysky2/kodi-standalone-service/compare/v1.8...v1.81

graysky commented on 2016-09-08 19:17 (UTC)

Replied in the bbs thread you linked.

zofiel commented on 2016-09-08 11:34 (UTC)

Since DBUS update, Kodi standalone doesn't works properly. Press home button and kodi freezes. Looking for a solution, I found this post: https://bbs.archlinux.org/viewtopic.php?id=216001&p=2 Deleting /usr/bin/dbus-launch --exit-with-session solved the issue I don't know If this option is not longer necessary

graysky commented on 2016-06-21 00:35 (UTC)

Good catch, thank you.

bananabrain commented on 2016-06-20 23:48 (UTC)

minor syntax error in readme.install, lines 61, 73

Tetz commented on 2016-06-10 04:19 (UTC)

I have to change all the tty7 references in the kodi.service file to tty1 to make it work on my system.

CandyAngel commented on 2016-04-06 22:24 (UTC)

@graysky: This occurred (on the same machine) on two successive fresh installations from the 2016-03-01 media (with both of those drivers). The change was not required when using the nouveau module. Kodi would also start with nvidia and the original ExecStart when the 'kodi' user was 'sudo su -l'd to. When starting kodi.service "as-is" with the nvidia or nvidia-340xx drivers, Xorg.0.log contains: [ 14.098] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c1 [ 14.100] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 8 paused 1 [ 14.100] (EE) Error systemd-logind returned paused fd for drm node [..snip..] [ 14.258] (==) Matched nouveau as autoconfigured driver 0 (and the nvidia driver is not matched at all) However, with the modification, systemd-logind is only mentioned once: [ 13.368] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration It may be important that this line is also included in my working Xorg.0.log: [ 13.367] (--) using VT number 2 Let me know if there is anything I can do to help isolate the problem! :)

graysky commented on 2016-04-05 19:03 (UTC)

@candy - That shouldn't be necessary. I have tested this on several boxes with the nvidia drivers installed (nvidia and nvidia-340xx) and it behaves as expected for me.

« First ‹ Previous 1 .. 11 12 13 14 15 16 17 18 19 20 21 22 Next › Last »