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.051762
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 2 3 4 5 6 7 .. 22 Next › Last »

graysky commented on 2023-10-01 11:50 (UTC)

I don't know about that pw.loop message. If the executable is running is the output defaulting to your HDMI or to another port of your graphics card?

a.s5n commented on 2023-10-01 11:45 (UTC) (edited on 2023-10-01 12:00 (UTC) by a.s5n)

yeah, it has been running and there is a message kodi-standalone[433]: [E] pw.loop [loop.c:67 pw_loop_new()] 0x557d4a793640: can't make support.system handle: No such file or directory

In additional, I have tried to add kodi.bin --standalone windowing=gbm and their WINDOWING env. No changes. Still black screen.

graysky commented on 2023-10-01 10:59 (UTC)

Is kodi running? ps aux | grep kodi

a.s5n commented on 2023-10-01 09:33 (UTC) (edited on 2023-10-01 11:45 (UTC) by a.s5n)

Hi everyone. I would like to figure out how to render kodi-gbm on small AMD SoC with out DE.

● kodi-gbm.service - Kodi standalone (GBM)
     Loaded: loaded (/usr/lib/systemd/system/kodi-gbm.service; enabled; preset: disabled)
     Active: active (running) since Sun 2023-10-01 08:56:57 UTC; 17min ago
   Main PID: 412 (kodi-standalone)
      Tasks: 0 (limit: 3972)
     Memory: 2.1M
        CPU: 15ms
     CGroup: /system.slice/kodi-gbm.service
             ‣ 412 /bin/sh /usr/bin/kodi-standalone

Oct 01 08:56:57 x systemd[1]: Started Kodi standalone (GBM).
Oct 01 08:56:57 x (andalone)[412]: pam_unix(login:session): session opened for user kodi(uid=968) by kodi(uid=0)

However, Display Port (DP) connected display just shows a recent fsck report after reboot. May I ask someone for a link about how to setup GBM environment?

  • dmesg | grep drm attached, here: https://gist.github.com/asteshin/760b67113dd7e7f45e69e53609630d20
  • Oct 01 08:56:58 x kernel: memfd_create() without MFD_EXEC nor MFD_NOEXEC_SEAL, pid=432 'kodi.bin'
  • kodi-standalone[433]: [E] pw.loop [loop.c:67 pw_loop_new()] 0x557d4a793640: can't make support.system handle: No such file or directory

ghen commented on 2023-02-07 12:25 (UTC)

Alternatively, run systemctl --global disable pipewire.socket (which was enabled automatically when installing pipewire) and reboot.

See also https://bugs.archlinux.org/task/77341

berturion commented on 2023-02-07 12:07 (UTC)

Hello, if you have no sound after the recent pipewire default installation on your Arch Linux system, you can edit /etc/conf.d/kodi-standalone and add:

KODI_AE_SINK=ALSA

Then restart your kodi service.

graysky commented on 2021-08-15 18:20 (UTC) (edited on 2021-08-16 11:33 (UTC) by graysky)

@wooptoo - Are you using the latest version? This was fixed weeks ago: https://github.com/graysky2/kodi-standalone-service/commit/33dc37310fea769e5eedbc2615850c93961b44e1

Also, the ExecStop is needed or else kodi does not exit cleanly/you lose data. See commit msg: https://github.com/graysky2/kodi-standalone-service/commit/34515c33387381c996c1760619d8554628910321

wooptoo commented on 2021-08-15 15:32 (UTC) (edited on 2021-08-15 15:34 (UTC) by wooptoo)

The kodi-x11.service now fails since it can't find the kodi-x11 binary. Replacing the ExecStart directive with the following fixed it:

ExecStart=/usr/bin/xinit /usr/bin/kodi --standalone -fs -- :0 -quiet -nolisten tcp vt1

Also the ExecStop line is not necessary since systemd kills all processed owned by the kodi user.

Complete file here https://gist.github.com/radupotop/5ed69a4fc0a06c9341a2cabd82639ee8

francoism90 commented on 2021-08-04 13:05 (UTC)

@graysky Turns out I'm an idiot.. changing the target (https://wiki.archlinux.org/title/Systemd#Targets) to graphical.target fixed the issue. :)

« First ‹ Previous 1 2 3 4 5 6 7 .. 22 Next › Last »