Search Criteria
Package Details: kodi-standalone-service 1.137-2
Package Actions
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.30 |
First Submitted: | 2014-11-05 20:25 (UTC) |
Last Updated: | 2024-07-06 08:38 (UTC) |
Dependencies (6)
- kodi (kodi-ext-gitAUR, kodi-gles)
- polkit (polkit-gitAUR, polkit-consolekitAUR)
- cage (cage-gitAUR) (optional) – for kodi-wayland.service
- wayland (wayland-gitAUR, wayland-asan-gitAUR, wayland-chromiumAUR) (optional) – for kodi-wayland.service
- xorg-server (xorg-server-gitAUR, xorg-server-bug865-issue1578AUR, xorg-server-bug865AUR) (optional) – for kodi-x11.service
- xorg-xinit (xorg-xinit-gitAUR) (optional) – for kodi-x11.service
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 22 Next › Last »
graysky commented on 2021-03-21 22:22 (UTC)
I added it since some users built on Arch ARM and caused them problems. Are you experiencing an issue with it?
ghen commented on 2021-03-21 21:09 (UTC)
That's not really relevant. It doesn't make sense to "build" separate i686, x86_64, and soon maybe x86_64-v3 versions of this non-binary package.
graysky commented on 2021-03-21 20:58 (UTC)
khvalera commented on 2021-03-21 20:23 (UTC)
why is the architecture
x86_64
specified and notany
?francoism90 commented on 2021-03-02 07:50 (UTC)
Do you guys run
kodi-wayland
orkodi-x11
as standalone? I'm thinking of moving to Wayland as standalone.graysky commented on 2020-12-14 20:37 (UTC)
@ghen - the issue we are running into here is complex for kodi-x11 due to systemd and/or my lack of mastery of all its myriad nuances. For one, we are starting xorg-server and then starting kodi within in one step which led to a bit of confusion and discussion to get it to both start and stop properly[1,2].
Beyond that, differences in
systemctl stop kodi-x11
andsystemctl reboot
caused me to make the most recent change removing thePAMName=
so I could get the entire thing under the system.slice and out of the user.slice[3].I am open to suggestions to limit the kodi user to just the physical keyboard.
ghen commented on 2020-12-14 20:19 (UTC)
Thanks. Not sure it's a good idea to give kodi unrestricted access to all input devices though? (even if the user switches to another tty?)
graysky commented on 2020-12-14 19:58 (UTC) (edited on 2020-12-14 20:02 (UTC) by graysky)
@ghen - I think kodi may need to be in the input group now that the PAMName= directive is removed. EDIT: yep, I will fix and update. Thank you for the report.
ghen commented on 2020-12-14 18:51 (UTC)
I'm seeing the following in Xorg.log for all input devices, from power button to keyboard and mouse:
(EE) xf86OpenSerial: Cannot open device /dev/input/event4 Permission denied.
« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 22 Next › Last »