Kodi 20 fails to start with a segmentation fault
#16
Yeah - I'd go towards debian, especially as the kitty terminal is also affected from the same issue.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#17
That is what I am doing the last few days. The maintainer asked me to install the debug symbols for libc6 and kodi and post a new strace.
The problem is that apt can find libc6-dbg but not the equivalent one for kodi, kodi-bin-dbgsym, althought it does exist here
https://packages.debian.org/sid/kodi-bin-dbgsym

As for troubleshooting the current situation, I found this kodi enviromental variable: KODI_GL_INTERFACE. But starting kodi with 
Code:
$ export KODI_GL_INTERFACE=GLES
$ kodi
returns the same error. I think this is the closest I can get to qt5's behavior that makes the apps launch with the qt5gui gles package.

And that's all for today. I have some health issues since 12 hours ago (possibly post-covid ones, again) and I may visit the hospital later, so please excuse any delays in answering. Thank you for your understanding.
Reply
#18
shell:

echo "deb http://deb.debian.org/debian-debug sid-debug main contrib non-free" > /etc/apt/sources.list.d/sid-debug.list
apt-get update
apt-get install kodi-bin-dbgsym

Replace sid with whichever debian you use, ie bookworm, bullseye etc.
Maintainer of Kodi from Debian | Got an issue with Kodi from Debian? Report it here: Kodi from Debian - Support Thread
Reply
#19
I think I found something...
Earlier, I was searching my distro's package to see if they provide a .service file for systemd. And I came accross this
https://packages.debian.org/sid/amd64/kodi-bin/filelist

That lib on line 4 means that kodi 20 demands a cpu with sse4 instruction set? That was the first thing I thought, but then I noticed that its older versions also have that lib, e.g. 19.1 and 19.4 from stable and stable-backports respectively.
https://packages.debian.org/bullseye/amd...n/filelist
https://packages.debian.org/bullseye-bac...n/filelist

---edit
And I just tested le11b1 which came out yesterday and comes with kodi 20. Kodi launches with no issues. I even installed its terminal "addon" to check if it really uses nvidia and not nouveau, and it does use nvidia!
Reply
#20
As it seems, I am not the only one facing issues with kodi 20 on nvidia 340
https://forum.kodi.tv/showthread.php?tid=371747
https://github.com/xbmc/xbmc/issues/22491

So, apart from my forementioned question about which opengl version is required by kodi 20, I have a new one. How can I tell if kodi tries to use wayland? Because all those wayland libs made me anxious Big Grin

---edit
(deleted because I already mentioned le above)
Reply
#21
Here is THE log of libreelec 11b1, in case anyone finds something useful in it. It contains kodi's log and journalctl stuff.
http://ix.io/4ntd

The only useful thing I found in there is this bit
 
Code:
Feb 08 16:01:14.698463 le11 xorg-launch[929]: ================ WARNING WARNING WARNING WARNING ================
Feb 08 16:01:14.698463 le11 xorg-launch[929]: This server has a video driver ABI version of 25.2 that this
Feb 08 16:01:14.698463 le11 xorg-launch[929]: driver does not officially support.  Please check
Feb 08 16:01:14.698463 le11 xorg-launch[929]: http://www.nvidia.com/ for driver updates or downgrade to an X
Feb 08 16:01:14.698463 le11 xorg-launch[929]: server with a supported driver ABI.
but this is old news. The workaround for making nvidia legacy work with xorg 21.x is to add 
 
Code:
Option "IgnoreABI" "1"
and it exists for a year now, since Febryary 2022. It also comes "preinstalled" with nvidia 340 on debian since then.

---edit
I just noticed that the log shows my public ip, and in TWO lines! Removing things like that should be allowed by the rules and it should not qualify as deduction!
Reply
#22
As some manjaro user suggested in the relevant issue on github, launching kodi like so
Code:
$ LD_PRELOAD=/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 kodi
works. On my end though, it still pops these in the terminal
Code:
[W][05047.389255] pw.conf      | [          conf.c:  939 try_load_conf()] can't load config client.conf: No such file or directory
[E][05047.389421] pw.conf      | [          conf.c:  963 pw_conf_load_conf_for_context()] can't load default config client.conf: No such file or directory
but I do not think they are something important.
Reply
#23
Those are not imprtant but caused by pipewire "highjacking" the pulseaudio sink of kodi.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#24
I use neither pipewire, nor pulseaudio. Just plain alsa, since ever.
And alsa's outputs are listed inside kodi too, there is nothing related to pw or pa because I do not have them installed.
Reply
#25
Okay. Great if stuff is working great.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#26
I removed the "Debian 6.1" part from the title because, as seen in the relevant issue report on github, it is neither a debian nor a kernel (and probably not a kodi) issue.
Reply
#27
Time to put the padlock on this one. As it seems, the issue will be fixed on 20.2 because of this change.
https://github.com/xbmc/xbmc/pull/23226
Reply
#28
Finally, today's release of 20.2 fixed the issue. Please lock the thread.
Reply
#29
IBTL
Reply

Logout Mark Read Team Forum Stats Members Help
Kodi 20 fails to start with a segmentation fault0