Will push Kodi 20.4 to Mageia 9.
Advisory ======== Kodi has been updated to version 20.4 as a general bug fix release. References ========== Files ===== Uploaded to core/updates_testing kodi-eventclients-common-20.4-1.mga9 kodi-python-zeroconf-20.4-1.mga9 kodi-firewalld-services-20.4-1.mga9 kodi-python-20.4-1.mga9 kodi-python-xbmcclient-20.4-1.mga9 kodi-eventclient-kodi-send-20.4-1.mga9 kodi-python-bt-20.4-1.mga9 kodi-eventclient-ps3-20.4-1.mga9 kodi-texturepacker-20.4-1.mga9 kodi-eventclient-wiiremote-20.4-1.mga9 kodi-addon-devel-20.4-1.mga9 kodi-20.4-1.mga9 kodi-eventclients-common-20.4-1.mga9.tainted kodi-python-zeroconf-20.4-1.mga9.tainted kodi-firewalld-services-20.4-1.mga9.tainted kodi-python-20.4-1.mga9.tainted kodi-python-xbmcclient-20.4-1.mga9.tainted kodi-eventclient-kodi-send-20.4-1.mga9.tainted kodi-python-bt-20.4-1.mga9.tainted kodi-eventclient-ps3-20.4-1.mga9.tainted kodi-texturepacker-20.4-1.mga9.tainted kodi-eventclient-wiiremote-20.4-1.mga9.tainted kodi-addon-devel-20.4-1.mga9.tainted kodi-20.4-1.mga9.tainted from kodi-20.4-1.mga9.src.rpm
Assignee: smelror => qa-bugs
mga9, x64 10-core Intel Core i9-7900X NVIDIA GP102 [GeForce GTX 1080 Ti] nvidia 535.129.03 Installed the untainted version and tried to launch it and saw an immediate crash with: terminate called after throwing an instance of 'fmt::v9::format_error' what(): string pointer is null /usr/bin/kodi: line 181: 1401361 Aborted (core dumped) ${KODI_BINARY} $SAVED_ARGS Updated all the packages and tried again - same result. Launching from the menus results in an immediate crash as well. The log ends with this: 2024-02-24 17:16:23.164 T:1401361 info <general>: CApplication::CreateGUI - using the x11 windowing system 2024-02-24 17:16:23.164 T:1401361 info <general>: Checking resolution 16 2024-02-24 17:16:23.215 T:1401361 info <general>: RetroPlayer[RENDER]: Registering renderer factory for OpenGL 2024-02-24 17:16:23.221 T:1401361 error <general>: failed to initialize egl 2024-02-24 17:16:23.297 T:1401361 info <general>: Using visual 0x21 2024-02-24 17:16:23.333 T:1401361 error <general>: CWinSystemX11::XErrorHandler: BadValue (integer parameter out of range for operation), type:0, serial:97, error_code:2, request_code:152 minor_code:3 2024-02-24 17:16:23.333 T:1401361 error <general>: GLX Error: Could not create context This is the information for X11: Display: x11 server: X.org v: 1.21.1.8 with: Xwayland v: 22.1.9 driver: X: and xorg.conf contains this: Section "Device" Identifier "device1" VendorName "NVIDIA Corporation" BoardName "NVIDIA GeForce 745 series and later" Driver "nvidia" Option "DPMS" Option "DynamicTwinView" "false" Option "AddARGBGLXVisuals" EndSection This is a regression before the update as well. It is a long time since I tried it, but back in the day it used to work. There may be something critical missing from this system but it also fails in the same way on a neighbouring machine with Intel graphics.
CC: (none) => tarazed25
A rider to comment 2; Installed the pre-update version on a Ryzen 7 with Radeon graphics and it launched from the command line without any bother. The interface came up - appears stable. This seems to suggest that we need tests on a variety of hardware.
MGA9-64 Plasma, AMD Phenom II X4 910, AMD HD 8490 graphics. Updated to the core version first, with no installation issues. No additional packages were drawn in with the update. I used Kodi to start to play a couple of mp4 videos, and some IPTV channels, both of which use the H.264 codec. The previous configuration, with VAAPI hardware acceleration disabled, played them normally. I updated to the tainted version, and tried again. This time video was not displayed in either test. Checking the settings, I saw that hardware acceleration had been changed to enabled, the upstream default. Disabling it again allowed H.264 video to appear once more. I closed Kodi and ran it again four times, once after a reboot, and the configuration changes remained intact, so it looks like they should be OK until the next update. I suspect that if one user setting was changed back to the default, then any of the rest that had been altered were, too. Affected users are going to find this annoying, to say the least. I realize that this is not *our* fault, but it *is* against Mageia policy to alter user configurations if we can avoid it. Is there anything we can do about it?
(In reply to Thomas Andrews from comment #4) > I suspect that if one user setting was changed back to the default, then any > of the rest that had been altered were, too. Affected users are going to > find this annoying, to say the least. I realize that this is not *our* > fault, but it *is* against Mageia policy to alter user configurations if we > can avoid it. Is there anything we can do about it? No, there is nothing we can do about it. There is nothing in the configuration options that mentions anything about user config.
There were a few changes made to the build. 1. I enabled both Wayland and GBM as Build Requires 2. I also added both vdpau and vaapi as Build Requires I'm having issues building Kodi locally at the moment and am debugging to figure out what's wrong. Will probably push an update (20.4-1.1) when I've got everything sorted. Personall running Cauldron, so can't really test anything mga9 related.
MGA9-64 Plasma, i5-7500, Nvidia Quadro K620 (nvidia-current), Acer R240HY HD monitor. I updated the core version from the previous tainted version, rather than installed. All that updated was kodi itself. Running from a terminal, the GUI popped right up, and functioned as with the previous version. Videos and TV channels played. Curious, I looked at the hardware acceleration settings, and found that VDPAU is being used. Closing, I found this in the terminal: [tom@localhost ~]$ kodi libva info: VA-API version 1.16.0 libva info: Trying to open /usr/lib64/dri/nvidia_drv_video.so libva info: Found init function __vaDriverInit_1_16 libva info: va_openDriver() returns 0 No idea if that's important.
CC: (none) => andrewsfarm
(In reply to Thomas Andrews from comment #7) > > [tom@localhost ~]$ kodi > libva info: VA-API version 1.16.0 > libva info: Trying to open /usr/lib64/dri/nvidia_drv_video.so > libva info: Found init function __vaDriverInit_1_16 > libva info: va_openDriver() returns 0 > > No idea if that's important. I think it's a good thing. Looks like it found a VAAPI driver and is using it. On my system using a 1660S, I get % /usr/bin/kodi libva info: VA-API version 1.20.0 libva error: vaGetDriverNames() failed with unknown libva error
In reply to comment 3: Spoke too soon. Managed to play a local video but most of the other options were too awkward to configure - right out of my depth. Loaded a DVD but could not lay it. All the VOBs and IFO sections were listed but it would not play and actually froze up. Had to zap the pid to get rid of it. Could not add a weather service. There seemed to be no way to specify the BBC for instance. Tried the suggested NOAA but no dice. Giving up on this.
(In reply to Len Lawrence from comment #9) > In reply to comment 3: > Spoke too soon. Managed to play a local video but most of the other options > were too awkward to configure - right out of my depth. Loaded a DVD but > could not lay it. All the VOBs and IFO sections were listed but it would > not play and actually froze up. Had to zap the pid to get rid of it. > Could not add a weather service. There seemed to be no way to specify the > BBC for instance. Tried the suggested NOAA but no dice. > > Giving up on this. DVD's only work with the tainted version, afaik. This is because the tainted version includes the dvdcss package.
(In reply to Stig, comment #10) I installed lib64dvdcss2 from tainted manually to get the DVD recognised. On the second attempt the interface still froze up. Is there something else needed? Beginning to see the light - commercial DVDs need the whole tainted version of kodi which I have not yet tried.
(In reply to Thomas Andrews in comment 7) > libva info: VA-API version 1.16.0 > libva info: Trying to open /usr/lib64/dri/nvidia_drv_video.so > libva info: Found init function __vaDriverInit_1_16 > libva info: va_openDriver() returns 0 That is what I get with the Intel/Intel system and the interface starts and crashes in a few milliseconds. If the vaapi driver is the problem then there is no way to disable it without the interface. The nvidia system throws the format error and fails to establish the interface. Shall try the tainted update tomorrow on all three systems. On the question of weather services - should the suggested sources not just be accepted? Or do you have to go looking for extra plugins?
(In reply to Stig-Ørjan Smelror from comment #1) > Advisory <snip> > from kodi-20.4-1.mga9.src.rpm the tainted src.rpm shouldn't be forgotten when uploading the advisory
CC: (none) => marja11Source RPM: (none) => kodi-20.2-1.mga9 kodi-20.2-1.mga9.tainted
Keywords: (none) => advisory
Continuing the saga. Remembered that this system had been used to test vdpau some time ago and that there is an environment variable which helped with that: .bashrc contains export LIBVA_DRIVER_NAME=i965 So I commented that out and logged in again but kodi still fails to launch. There is still a core dump and it still issues the earlier error: libva info: VA-API version 1.16.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: va_openDriver() returns -1 libva info: Trying to open /usr/lib64/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_16 libva error: /usr/lib64/dri/i965_drv_video.so init failed libva info: va_openDriver() returns -1 libva info: VA-API version 1.16.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: va_openDriver() returns -1 libva info: Trying to open /usr/lib64/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_16 libva error: /usr/lib64/dri/i965_drv_video.so init failed libva info: va_openDriver() returns -1 terminate called after throwing an instance of 'fmt::v9::format_error' what(): string pointer is null /usr/bin/kodi: line 181: 2760155 Aborted (core dumped) ${KODI_BINARY} $SAVED_ARGS Since there is no way for the user to configure kodi externally I think that the graphics driver problem looks like an upstream matter. The format error might be a consequence of the driver failure. Having said that, how is it that other users can launch kodi successfully? This implies that the user environment may have something to do with it. Speaking from Mate just now but testing it in Plasma does not seem to help although, not being a habitual Plasma user, there may well be things missing from my Plasma environment. Looking at lib64kf5 there are 160 packages, with a mixture of versions. $ path /home/lcl/bin /home/lcl/bin /usr/local/bin /usr/bin /bin /usr/local/games /usr/games /usr/local/sbin /usr/sbin /usr/lib64/qt5/bin /usr/lib64/qt6/bin /usr/lib64/qt4/bin /usr/lib/jvm/java-17-openjdk-17.0.8.0.7-1.mga9.x86_64/jre /home/lcl/.local/bin /home/lcl/bin /usr/lib/jvm/java-17-openjdk-17.0.8.0.7-1.mga9.x86_64/jre which all comes from: export PATH=/home/lcl/bin:$PATH:/usr/lib/jvm/java-17-openjdk-17.0.8.0.7-1.mga9.x86_64/jre
Just tried the tainted version with the same result - immediate crash. Note that the package names had to be changed from e.g. kodi-20.4-1.mga9.tainted to kodi-20.4-1.1.mga9.tainted ....
(In reply to stig in comment #6) Just noticed that you mentioned the change to 4.1.1 there. I used that version because the posted version could not be found. Went to the mirror site to confirm that.
Thanks Len. I think I've found one of the problems. It's an update checker that, when I removed it locally, made my clean Kodi install to launch (on Cauldron) without issue. There is also an issue with how Kodi tries to locate its Addons and I do have a hack that works, but am not really happy with. I may push it anyway, just to have something working. This'll be 20.4.1-2.
(removing the "advisory" keyword so it won't be forgotten to update the advisory in SVN after the updated packages are built)
Keywords: advisory => (none)
(In reply to Stig-Ørjan Smelror from comment #17) > Thanks Len. > > I think I've found one of the problems. It's an update checker that, when I > removed it locally, made my clean Kodi install to launch (on Cauldron) > without issue. > > There is also an issue with how Kodi tries to locate its Addons and I do > have a hack that works, but am not really happy with. I may push it anyway, > just to have something working. > > This'll be 20.4.1-2. Issues building the new testing packages? I still see the previous ones