[jim_p]

So, I used kodi a couple of hours ago (I actually opened it to renew twitch's api key), when it was on v19.
I got the upgrade to v20 a few minutes ago and now kodi does not launch at all! This is what pops out in the terminal
 

Code:

$ kodi
[W][00950.523123] pw.conf      | [          conf.c:  939 try_load_conf()] can't load config client.conf: No such file or directory
[E][00950.524845] pw.conf      | [          conf.c:  963 pw_conf_load_conf_for_context()] can't load default config client.conf: No such file or directory
Segmentation fault (core dumped)
Crash report available at /home/jim/kodi_crashlog-20230124_201422.log

this pops out it dmesg
 

Code:

[  866.924006] kodi.bin[3435]: segfault at 8 ip 00007f3739676b76 sp 00007ffd84f2e9c8 error 4 in libc.so.6[7f37395f3000+155000] likely on CPU 0 (core 0, socket 0)
[  866.924029] Code: 00 00 66 90 66 0f ef c0 66 0f ef c9 66 0f ef d2 66 0f ef db 48 89 f8 48 89 f9 48 81 e1 ff 0f 00 00 48 81 f9 cf 0f 00 00 77 6a <f3> 0f 6f 20 66 0f 74 e0 66 0f d7 d4 85 d2 74 04 0f bc c2 c3 48 83

and this is what the forementioned log file says
https://paste.debian.net/hidden/990fefcb/

I deleted the entire ~/.kodi folder too, so its installation is as clean as it will ever be. 

If it helps, almost all my qt5 apps have an issue with some gl library since the upgrade to kernel 6.1 and fail to launch, but I can not find out which one.

[izprtxqkft]

based on your log it is "normal behavior" for kodi to crash with this "GLX Error: vInfo is NULL!"

https://duckduckgo.com/?q=GLX+Error%253A+vInfo+is+NULL!

i found this https://github.com/xbmc/xbmc/issues/17147 which has no resolution but does have clues

do not ask me why it says kodi 8.15 but was posted in 2020, that part makes no sense but the rest does

multiple results with kodi crashing and that message, it always leads back to os configuration, missing files, incomplete, etc

[jim_p]

I saw that too. The problem is that kodi 19 was working properly with that "bad" os configuration, so it is hard to say that everything was in place for kodi 19 and a few hours later something broke for kodi 20, when the onliest upgrade on the system was kodi itself... And I am not talking about building something from source, like the user on github did, neither building it straight from git that may contain bugs, which is also what the user on github did. I am using a properly built package for my distro, which in turn is built from the latest and stable version of the app and, thanks to apt, I have all its dependecies properly installed.

On a similar issue in the past, I have asked the question "has something changed about kodi's opengl requirements". The answer was no, because the issue was really related to the os not loading the proper gpu driver (first beta/rc versions of libreelec 10 on an old intel vga). So I am asking it again today. If needed, I can post a gdb log.

I will try downgrading to kernel 6.0 later today... because I can not downgrade my gpu's driver and undo the patch for 6.1. 

p.s. I get kodi from deb-multimedia since ever. Why not from the main repo? Because it lags behind on some versions and because the maintainers there do not package kodi-vfs-rar. However, I gave that kodi a try yesterday and the result was exactly the same as the one from dmo.

---edit
There is a small part, one line actually, that I ommited from the terminal output above because it has to do with another app on my system (anydesk). Kodi was unable to read something inside ~/.anydesk. I will get to it on a different thread.

[Klojum]

@basilgello How far r u with kernel 6.1 and Debian running Kodi?

[jim_p]

I downgraded to 6.0 a few minutes ago but the issue still happens, which (imho) means one thing: something broke with that patch which was added so that my gpu's driver can be built with kernel 6.1. If anyone has a different idea, please share. Even the slightest one, e.g. about how I can identify that patch, counts.

[basilgello]

Kernel 6.1 works for me without issues on bookworm. But dmo is not what I have control over.
kodi-vfs-rar is doable but it will live in contrib, not in main due to licensing issues.

Speaking of "vInfo is NULL", I have the patch that at least does not crash Kodi if opengl renderer is NULL.
But glxinfo and vainfo should also break with such setup. Did you try running them?

[izprtxqkft]

that was the nice way of me saying your system is broken and i have no clue what you have or havent done on the system itself, bookworm is the testing branch so maybe you found a bug during your *testing* you need to report to debian
it does appear a lot in regards to video driver issues

[jim_p]

First things first, because I have to write a lot.
I know that only my system is broken and I am searching for that broken part, that is why I did not generalize it as a "kodi issue on debian".
I do its updates daily (well, 4 times a day, right after the mirrors sync), I have these repos
- default debian repo (testing, unstable and experimental), since ever
- dmo (testing and unstable), since ever
- brave's, since April 2020
- sublime's, since December 2022
As you can see the onliest place I can get updates from important stuff like drivers, kernel etc is the default debian repo, so there is not a single possibility I created a frankendebian. I also get mpv, mplayer, smplayer, kodi etc from dmo since ever.
Last but not least, I do know how to file a bug report to debian, I have filled several dozens of them all these 15 years that I am on its rolling release branches, but I have stopped doing so since last April. I am keeping the reason to myself, but let's say it can be described with the phrase "no substantial support on major issue".
And that is all about me and debian. If anyone wants to ask something else, feel free to pm me.

Moving on to kodi and gl libs. I tried kodi from the main repo, but it has the same issue.
Moreover, a few days ago I noticed that all my qt5 apps (excluding smplayer and keepassxc) crashed at launch with a segfault. To fix that, I substituted libqt5gui5 with its inferior version of libqt5gui5-gles. That was the first clue I got that something is wrong with my gl libs. I double checked that with another debian unstable user who is on nvidia 340 and faces the same. I asked him if he notices the same on kodi (I do not even know if he uses kodi or not), but he has not replied yet.
If anyone is interested in a coredump, here is one (I ran coredumpctl debug right after kodi crashed)
https://paste.debian.net/1268410/

As for vainfo and glxinfo, they both run fine. Vainfo returns this, probably because I do not use a driver that does vaaapi but one that does vdpau
 

Code:

$ vainfo 
libva info: VA-API version 1.17.0
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
vaInitialize failed with error code -1 (unknown libva error),exit

and glxinfo returns this common, huge output, nothing special. 
https://paste.debian.net/hidden/0d841111/

p.s. Please excuse any delays in answering. I am facing some minor health issue and pain sometimes keeps me away from my pc.

[jim_p]

Minor update. That other user did not have kodi installed, but I asked him to install (from the default repo, he does not use dmo) it for me and he did. And he gets the same error.

So my initial question remains. What is kodi's new requirement on opengl libraries that changed from 19 to 20? On x11 that is, I do not use wayland.

[jim_p]

Do you know of any other app that is built with the same toolkit kodi is built? I thought it was built with sdl, so I installed retroarch which is sdl based too and it works as it should.
Then I discovered that kodi is not built with sdl, because it does not use it as a dependency

[wsnipex]

there is no toolkit, it's just OpenGL/GLES

[fritsch]

@sarbes Could you take a look - I "think" that I remember that the minimum compatible GL version was bumped along the way. From 2.1 to 3.0? I cannot  find the commit anymore, but I have something very  cloudy in mind concernig that.

[jim_p]

there is no toolkit, it's just OpenGL/GLES

Thank you. I just came accross kitty, which is a "gpu based terminal emulator" according to its description. It also fails to start and this is what its debug info can show

Code:

$ kitty --debug-gl
GL version string: '3.3.0 NVIDIA 340.108' Detected version: 3.3
Segmentation fault (core dumped)
$ kitty --debug-rendering
GL version string: '3.3.0 NVIDIA 340.108' Detected version: 3.3
Segmentation fault (core dumped)

I will keep looking for more apps until I find one with a helpful output.
Unfortunately, I can not use kernel 6.0 along with the previous package for my driver. I can install the old kernel, I can install the previous version of the package, but when it comes to building it, dkms fails to build it with 6.1 and it does not continue building it with 6.0.

I have also thought of testing libreelec 11 that comes with kodi 20, but I am looking for an image of it that is not nightly. Fyi, le 11 beta1 was tagged in their github a week ago.

[fritsch]

Might be a good time to file a bug with debian. As quite a lot OpenGL aplications are broken it seems?

[jim_p]

I did (actually I asked someone else to start it and then I continued it) and the maintainer said it should have no issues. It's bug number 1029681 in case anyone wants to check.

Back to opengl versions, because I missed your post earlier. Glxinfo reports 1.4 as the "glx version string" for both server and client

Code:

$ glxinfo | grep "glx version"
server glx version string: 1.4
client glx version string: 1.4

and further down it reports 3.3.0 as the opengl version

Code:

$ glxinfo | grep "OpenGL version"
OpenGL version string: 3.3.0 NVIDIA 340.108