Kodi Error - Kodi not starting

I am using the latest DietPi version. I also installed Docker for using pihole.

Now I installed Kodi via the Software Center.

After using the command “startkodi” the following error was shown:

        root@DietPi:~# startkodi
libva info: VA-API version 1.10.0
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
sh: 1: nmblookup: not found
sh: 1: nmblookup: not found
sh: 1: nmblookup: not found
sh: 1: nmblookup: not found
sh: 1: nmblookup: not found
sh: 1: nmblookup: not found
sh: 1: nmblookup: not found
^C

What can I do?

Not related question, why using docker? DietPi is offering Pihole natively and you could save docker overhead

Back to Kodi. Pls could you share some more system details. Are you using a RPi4?

Required Information

  • DietPi version | cat /boot/dietpi/.version
  • Distro version | echo $G_DISTRO_NAME $G_RASPBIAN
  • Kernel version | uname -a
  • SBC model | echo $G_HW_MODEL_NAME or (EG: RPi3)
root@DietPi:~# cat /boot/dietpi/.version
G_DIETPI_VERSION_CORE=7
G_DIETPI_VERSION_SUB=7
G_DIETPI_VERSION_RC=3
G_GITBRANCH='master'
G_GITOWNER='MichaIng'



echo $G_DISTRO_NAME $G_RASPBIAN
bullseye 1



root@DietPi:~# uname -a
Linux DietPi 5.10.63-v7l+ #1459 SMP Wed Oct 6 16:41:57 BST 2021 armv7l GNU/Linux



echo $G_HW_MODEL_NAME
RPi 4 Model B (armv7l)

ok on RPi4 we have a know issue to start Kodi. Currently we are not sure why Kodi is started on background. Still something we don’t have a solution for.

MichaIng
FYI

Do I have to uninstall it?

well you could removed it as it’s not working at the moment.

Where can I find more information about the current status?

How long would it take to fix the Problem with Raspi 4?

Actually it’s still not clear why this happen on RPi4. Something we would need to check with RPi and or Kodi guys, if I understood correct from our developer

Any new information to solve the problem?

Progress is being made, check this post here: How to install KODI 18.7 on Bullseye? - #17 by MichaIng

yes, RPi devs did some development and on RPi4 64bit it was working on my test I did this week



DietPi-Software
─────────────────────────────────────────────────────
 Step: Install completed

[  OK  ] DietPi-Survey | Purging survey data
[ SUB1 ] DietPi-Services > restart
[  OK  ] DietPi-Services | restart : avahi-daemon
[  OK  ] DietPi-Services | restart : proftpd
[  OK  ] DietPi-Services | restart : php7.4-fpm
[  OK  ] DietPi-Services | restart : nginx
[  OK  ] DietPi-Services | restart : lighttpd
[  OK  ] DietPi-Services | restart : cron
root@DietPi:~# startkodi
-bash: startkodi: command not found

After reboot:

root@DietPi:~# startkodi
failed to open zone.tab
error: XDG_RUNTIME_DIR not set in the environment.
libva info: VA-API version 1.10.0
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
^C

Something is still wrong?

usually not. Kodi should start on an attached screen.

So I should use an HDMI cable from my Raspi to my TV and then I try the command again?

yes Kodi as an application that require a monitor. It’s not something you could run on a SSH client.

Indeed, like all GUI applications. For X11, there is an X11 forwarding feature, which is by default enabled on OpenSSH as well as on Dropbear SSH servers, and which can be enabled on PuTTY. Then one needs to run a local X server on the client system, e.g. Xming on Windows. But I don’t think passing a playing video through SSH will work at all, and the RPi Kodi build uses GBM/DRM and not the X server, so no chance.

:thinking:
So I can not use Kodi via Raspi 4 to my TV Screen with HDMI?

startkodi
failed to open zone.tab
error: XDG_RUNTIME_DIR not set in the environment.
libva info: VA-API version 1.10.0
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)

I thought that the app would Start as media center on the Raspi.

of course you can use Kodi an a HDMI connected screen

But I only have no kodi on my screen and the above error code in my terminal.

messages on console are ok. Try following

/boot/dietpi/func/dietpi-set_hardware rpi-opengl vc4-kms-v3d
startkodi