Package Details: kodi-git r67165.504c69cc3b2b-1

Git Clone URL: https://aur.archlinux.org/kodi-git.git (read-only, click to copy)
Package Base: kodi-git
Description: A software media player and entertainment hub for digital media (master branch, gles renderer)
Upstream URL: https://kodi.tv
Licenses: GPL2
Conflicts: kodi, kodi-gbm, kodi-gles, kodi-wayland, kodi-x11
Provides: kodi-common, kodi-gbm, kodi-wayland, kodi-x11
Submitter: BlackIkeEagle
Maintainer: graysky
Last Packager: graysky
Votes: 85
Popularity: 0.000672
First Submitted: 2014-10-23 06:38 (UTC)
Last Updated: 2024-12-08 16:30 (UTC)

Dependencies (105)

Required by (0)

Sources (9)

Pinned Comments

graysky commented on 2022-06-11 11:49 (UTC)

@laichiaheng - kodi is bound to a specific version of ffmpeg which is generally older than Arch's package. We avoid incompatibilities by using that specific version (ie internal ffmpeg). Recommend that you build kodi in clean chroot. See: https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot

I wrote a script that automates much of that called clean-chroot-manager offered here in the AUR.

Latest Comments

« First ‹ Previous 1 .. 21 22 23 24 25 26 27 28 29 30 31 .. 55 Next › Last »

BlackIkeEagle commented on 2014-07-31 05:41 (UTC)

I need to look into it further, its a start ;)

Beretta92 commented on 2014-07-30 20:24 (UTC)

Thanks, works but not the keyboard

BlackIkeEagle commented on 2014-07-30 15:04 (UTC)

as a current workaround you can use: create /etc/systemd/system/getty@tty7.service.d/autologin.conf (with folders) autologin.conf: [Service] ExecStart= ExecStart=-/usr/bin/agetty --autologin xbmc --noclear %I 38400 linux edit /var/lib/xbmc/.bashrc # # ~/.bashrc # /usr/bin/xinit /usr/bin/dbus-launch --exit-with-session /usr/bin/xbmc-standalone -- :0 -nolisten tcp $ systemctl disable xbmc $ systemctl enable getty@tty7 $ reboot (i did not test any other way, only control on my standalone system is IR remote and ssh ) xbmc is working again, note i'll try to find an other option which is simpler, but this works for now

Beretta92 commented on 2014-07-30 13:18 (UTC)

weird: [root@Serveur ~]# systemctl restart xbmc.service [root@Serveur ~]# systemctl status xbmc.service ● xbmc.service - Starts instance of XBMC using xinit Loaded: loaded (/usr/lib/systemd/system/xbmc.service; enabled) Active: active (running) since mer. 2014-07-30 16:11:34 CEST; 3s ago Main PID: 551 (xinit) CGroup: /system.slice/xbmc.service ‣ 551 /usr/bin/xinit /usr/bin/dbus-launch --exit-with-session /usr/bin/xbmc-standalone -- :0 -nolisten tcp vt7 juil. 30 16:11:34 Serveur systemd[1]: Started Starts instance of XBMC using xinit. juil. 30 16:11:34 Serveur systemd[551]: pam_unix(login:session): session opened for user xbmc by (uid=0) But nothing on screen

Beretta92 commented on 2014-07-30 12:08 (UTC)

thanks, if it helps: systemctl status xbmc.service ● xbmc.service - Starts instance of XBMC using xinit Loaded: loaded (/usr/lib/systemd/system/xbmc.service; enabled) Active: failed (Result: exit-code) since mer. 2014-07-30 14:59:25 CEST; 1min 11s ago Process: 363 ExecStart=/usr/bin/xinit /usr/bin/dbus-launch --exit-with-session /usr/bin/xbmc-standalone -- :0 -nolisten tcp vt7 (code=exited, status=1/FAILURE) Main PID: 363 (code=exited, status=1/FAILURE) juil. 30 14:59:09 Serveur systemd[363]: pam_unix(login:session): session opened for user pavanpe by (uid=0) juil. 30 14:59:25 Serveur xinit[363]: /usr/bin/xinit: unable to connect to X server: Connection refused juil. 30 14:59:25 Serveur xinit[363]: /usr/bin/xinit: server error juil. 30 14:59:25 Serveur systemd[1]: xbmc.service: main process exited, code=exited, status=1/FAILURE juil. 30 14:59:25 Serveur systemd[1]: Unit xbmc.service entered failed state.

BlackIkeEagle commented on 2014-07-29 20:48 (UTC)

@Beretta92 I'll check but it will be tomorow at best

Beretta92 commented on 2014-07-29 20:42 (UTC)

yes, with the xbmc.service

BlackIkeEagle commented on 2014-07-29 20:41 (UTC)

@Beretta92 ? standalone ? I did not yet have the time to update my media machine to test standalone

Beretta92 commented on 2014-07-29 20:23 (UTC)

Any ideas on how to get it running with new xorg?