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
I am not sure if this may be useful for Mageia9 updates : Jani Välimaa (Wally) has updated Kodi to version 20.5 inside Cauldron with some tricks that are perhaps specific to build it for Cauldron... I don't know if anybody could test it inside Cauldron
CC: (none) => philippedidier
Hi, With no familiarity with Kodi, I installed 20.4.1.1.mga9.tainted. (on a almost clean fully updated spare M9 installation, not via qarepo) Fired up and appeared to run OK, it found my genuine commercial movie DVD I'd poked in an external USB blu-ray player, handled the menu OK and at least started playing the movie.. Didn't persist beyond that. No issues found. $ inxi -C CPU: Info: quad core model: Intel Core i7-7700K bits: 64 type: MT MCP cache: L2: 1024 KiB Speed (MHz): avg: 800 min/max: 800/4500 cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 $ inxi -G Graphics: Device-1: NVIDIA GP102 [GeForce GTX 1080 Ti] driver: nouveau v: kernel Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo Display: x11 server: X.org v: 1.21.1.8 with: Xwayland v: 22.1.9 driver: X: loaded: nouveau,v4l dri: nouveau gpu: nouveau resolution: 1: 2560x1440~60Hz 2: 2560x1440~60Hz API: OpenGL v: 4.3 Mesa 24.0.5 renderer: NV132
CC: (none) => tablackwell
This was the only stuff seen in the text box I launched it from: (xfce) Didn't stop it working. tony@testm9 ~]$ kodi libEGL warning: failed to get driver name for fd -1 libEGL warning: MESA-LOADER: failed to retrieve device information libEGL warning: failed to get driver name for fd -1 libva info: VA-API version 1.21.0 libva info: Trying to open /usr/lib64/dri/nouveau_drv_video.so libva info: Found init function __vaDriverInit_1_21 libva info: va_openDriver() returns 0
(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. Stig, any progress with this? I'd like to get this longstanding bug to move along. In the meantime, I recently tried out Kodi on my HP Pavilion. It had been so long since I had opened it that I checked for which version was installed, finding it was 20.2. When I did that, a notice popped up that 21.0 is the latest stable version, and indeed there is a relatively recent bug report to update Cauldron to that version. Should we be updating mga9 to 21.0 as well? As for this bug, I updated the Pavilion to 20.4.1-1, and had no issues. I had only played videos with it before, but this time I installed the iptvsimple add-on from our repos, and configured it as I had on other hardware, and it works the same on the Pavilion. I have not seen any crashes like Len has seen, on any hardware.
MGA9-64 Plasma Wayland on HP-Pavillion Installed core versions Kodi runs, but at CLI: $ kodi libva info: VA-API version 1.22.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 error: failed to resolve wl_drm_interface(): /lib64/libEGL_mesa.so.0: undefined symbol: wl_drm_interface libva error: /usr/lib64/dri/i965_drv_video.so init failed libva info: va_openDriver() returns -1 and mpg or avi file opens and plays, but only sound, no video. Hardware: Description: Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller
CC: (none) => herman.viaene
MGA9-64, Xfce, Celeron N2840, Chromebook The following 19 packages are going to be installed: - kodi-20.4-1.1.mga9.tainted.x86_64 - lib64cec6-6.0.2-3.mga9.x86_64 - lib64crossguid0-0.2.3-0.git20190529.1.mga9.x86_64 - lib64fmt9-9.1.0-1.mga9.x86_64 - lib64fstrcmp0-0.7.D001-4.mga9.x86_64 - lib64imagequant0-2.18.0-1.mga9.x86_64 - lib64iso9660_11-2.1.0-4.1.mga9.x86_64 - lib64lirc0-0.10.2-5.mga9.x86_64 - lib64p8-platform2-2.1.0.1-4.mga9.x86_64 - lib64pcre1-8.45-3.mga9.x86_64 - lib64pcrecpp0-8.45-3.mga9.x86_64 - lib64plist2.0_3-2.2.0-4.mga9.x86_64 - lib64shairplay0-0.9.0-0.git20180824.4.mga9.x86_64 - lib64spdlog1.11-1.11.0-4.mga9.x86_64 - lib64tinyxml0-2.6.2-14.1.mga9.x86_64 - lib64usb-compat0.1_4-0.1.5-11.mga9.x86_64 - lib64waylandpp1-1.0.0-1.mga9.x86_64 - libplist-2.2.0-4.mga9.x86_64 - python3-pillow-9.2.0-3.2.mga9.x86_64 81MB of additional disk space will be used. 31MB of packages will be retrieved. --- rebooted I picked Kodi from menu and was able to select an mp4/h264 movie and play it. Options seemed to work as expected. Menu items flowed as I would expect. Haven't tried this on nvidia, but works on this.
CC: (none) => brtians1
I see updated package without new lists, so here is the list Advisory ======== Kodi has been updated to version 20.4 as a general bug fix release. RPMs from 'core-updates_testing' ======================== kodi-20.4-1.1.mga9 kodi-addon-devel-20.4-1.1.mga9 kodi-eventclient-kodi-send-20.4-1.1.mga9 kodi-eventclient-ps3-20.4-1.1.mga9 kodi-eventclient-wiiremote-20.4-1.1.mga9 kodi-eventclients-common-20.4-1.1.mga9 kodi-firewalld-services-20.4-1.1.mga9.noarch.rpm kodi-python-20.4-1.1.mga9.noarch.rpm kodi-python-bt-20.4-1.1.mga9.noarch.rpm kodi-python-xbmcclient-20.4-1.1.mga9.noarch.rpm kodi-python-zeroconf-20.4-1.1.mga9.noarch.rpm kodi-texturepacker-20.4-1.1.mga9 RPMs from 'tainted-updates_testing' ======================== kodi-20.4-1.1.mga9.tainted kodi-addon-devel-20.4-1.1.mga9.tainted kodi-eventclient-kodi-send-20.4-1.1.mga9.tainted kodi-eventclient-ps3-20.4-1.1.mga9.tainted kodi-eventclient-wiiremote-20.4-1.1.mga9.tainted kodi-eventclients-common-20.4-1.1.mga9.tainted kodi-firewalld-services-20.4-1.1.mga9.tainted.noarch.rpm kodi-python-20.4-1.1.mga9.tainted.noarch.rpm kodi-python-bt-20.4-1.1.mga9.tainted.noarch.rpm kodi-python-xbmcclient-20.4-1.1.mga9.tainted.noarch.rpm kodi-python-zeroconf-20.4-1.1.mga9.tainted.noarch.rpm kodi-texturepacker-20.4-1.1.mga9.tainted SRPMs from 'core-updates_testing' ======================== kodi-20.4-1.1.mga9 SRPMs from 'tainted-updates_testing' ======================== kodi-20.4-1.1.mga9.tainted
Status comment: (none) => Current list in comment 27
RH x86_64 Test core version LC_ALL=C urpmi kodi To satisfy dependencies, the following packages are going to be installed: Package Version Release Arch (medium "QA Testing (64-bit)") kodi 20.4 1.1.mga9 x86_64 (medium "Core Release (distrib1)") lib64cec6 6.0.2 3.mga9 x86_64 lib64crossguid0 0.2.3 0.git2019052> x86_64 lib64fstrcmp0 0.7.D001 4.mga9 x86_64 lib64p8-platform2 2.1.0.1 4.mga9 x86_64 lib64pcrecpp0 8.45 3.mga9 x86_64 lib64shairplay0 0.9.0 0.git2018082> x86_64 lib64waylandpp1 1.0.0 1.mga9 x86_64 (medium "Core Updates (distrib3)") lib64tinyxml0 2.6.2 14.1.mga9 x86_64 77MB of additional disk space will be used. 30MB of packages will be retrieved. Proceed with the installation of the 9 packages? (Y/n) y https://mirror.math.princeton.edu/pub/mageia/distrib/9/x86_64/media/core/release/lib64waylandpp1-1.0.0-1.mga9.x86_64.rpm https://mirror.math.princeton.edu/pub/mageia/distrib/9/x86_64/media/core/release/lib64p8-platform2-2.1.0.1-4.mga9.x86_64.rpm https://mirror.math.princeton.edu/pub/mageia/distrib/9/x86_64/media/core/release/lib64pcrecpp0-8.45-3.mga9.x86_64.rpm https://mirror.math.princeton.edu/pub/mageia/distrib/9/x86_64/media/core/release/lib64cec6-6.0.2-3.mga9.x86_64.rpm https://mirror.math.princeton.edu/pub/mageia/distrib/9/x86_64/media/core/release/lib64shairplay0-0.9.0-0.git20180824.4.mga9.x86_64.rpm https://mirror.math.princeton.edu/pub/mageia/distrib/9/x86_64/media/core/release/lib64fstrcmp0-0.7.D001-4.mga9.x86_64.rpm https://mirror.math.princeton.edu/pub/mageia/distrib/9/x86_64/media/core/release/lib64crossguid0-0.2.3-0.git20190529.1.mga9.x86_64.rpm https://mirror.math.princeton.edu/pub/mageia/distrib/9/x86_64/media/core/updates/lib64tinyxml0-2.6.2-14.1.mga9.x86_64.rpm installing /var/cache/urpmi/rpms/lib64shairplay0-0.9.0-0.git20180824.4.mga9.x86_64.rpm /var/cache/urpmi/rpms/lib64tinyxml0-2.6.2-14.1.mga9.x86_64.rpm /var/cache/urpmi/rpms/lib64cec6-6.0.2-3.mga9.x86_64.rpm /var/cache/urpmi/rpms/lib64crossguid0-0.2.3-0.git20190529.1.mga9.x86_64.rpm //home/katnatek/qa-testing/x86_64/kodi-20.4-1.1.mga9.x86_64.rpm /var/cache/urpmi/rpms/lib64fstrcmp0-0.7.D001-4.mga9.x86_64.rpm /var/cache/urpmi/rpms/lib64p8-platform2-2.1.0.1-4.mga9.x86_64.rpm /var/cache/urpmi/rpms/lib64waylandpp1-1.0.0-1.mga9.x86_64.rpm /var/cache/urpmi/rpms/lib64pcrecpp0-8.45-3.mga9.x86_64.rpm Preparing... ################################################################################################## 1/9: lib64pcrecpp0 ################################################################################################## 2/9: lib64waylandpp1 ################################################################################################## 3/9: lib64p8-platform2 ################################################################################################## 4/9: lib64cec6 ################################################################################################## 5/9: lib64fstrcmp0 ################################################################################################## 6/9: lib64crossguid0 ################################################################################################## 7/9: lib64tinyxml0 ################################################################################################## 8/9: lib64shairplay0 ################################################################################################## 9/9: kodi ################################################################################################## Play some videos not issues
RH x86_64 Test tainted version LC_ALL=C urpmi --auto --auto-update adding 66 new rpms not available in existing hdlist replacing /var/cache/urpmi/partial/synthesis.hdlist.cz with synthesis.hdlist.cz.tmp updating /var/cache/urpmi/partial/MD5SUM updated medium "QA Testing (32-bit)" medium "QA Testing (64-bit)" is up-to-date medium "Core Release (distrib1)" is up-to-date medium "Core Updates (distrib3)" is up-to-date medium "Nonfree Release (distrib11)" is up-to-date medium "Nonfree Updates (distrib13)" is up-to-date medium "Tainted Release (distrib21)" is up-to-date medium "Tainted Updates (distrib23)" is up-to-date medium "Core 32bit Release (distrib31)" is up-to-date medium "Core 32bit Updates (distrib32)" is up-to-date medium "Nonfree 32bit Release (distrib36)" is up-to-date medium "Tainted 32bit Release (distrib41)" is up-to-date medium "Tainted 32bit Updates (distrib42)" is up-to-date installing kodi-20.4-1.1.mga9.tainted.x86_64.rpm from //home/katnatek/qa-testing/x86_64 Preparing... ################################################################################################## 1/1: kodi ################################################################################################## 1/1: removing kodi-20.4-1.1.mga9.x86_64 ################################################################################################## Play videos and audio without issues, would like to do a more deep test with other packages but never use before this application If Len could confirm the packages works for him we could validate this
A bit late in the day now so I shall look into it tomorrow. Thanks.
mga9, x64 Installed kodi from Core Release. Problem running that, as before. Updated from testing. $ kodi libva info: VA-API version 1.22.0 libva info: User environment variable requested driver 'i965' 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.22.0 libva info: User environment variable requested driver 'i965' 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: 1121688 Aborted (core dumped) ${KODI_BINARY} $SAVED_ARGS Crash report available at /home/lcl/kodi_crashlog-20240828_154042.log Report attached. These are the RPMs in the local repository: kodi-20.4-1.1.mga9.x86_64.rpm kodi-addon-devel-20.4-1.1.mga9.x86_64.rpm kodi-eventclient-kodi-send-20.4-1.1.mga9.x86_64.rpm kodi-eventclient-ps3-20.4-1.1.mga9.x86_64.rpm kodi-eventclients-common-20.4-1.1.mga9.x86_64.rpm kodi-eventclient-wiiremote-20.4-1.1.mga9.x86_64.rpm kodi-firewalld-services-20.4-1.1.mga9.noarch.rpm kodi-python-20.4-1.1.mga9.noarch.rpm kodi-python-bt-20.4-1.1.mga9.noarch.rpm kodi-python-xbmcclient-20.4-1.1.mga9.noarch.rpm kodi-python-zeroconf-20.4-1.1.mga9.noarch.rpm kodi-texturepacker-20.4-1.1.mga9.x86_64.rpm I have checked all the dependencies listed in comment #28 and they are all installed. Running this in Mate. $ inxi -G Graphics: Device-1: Intel Alder Lake-P Integrated Graphics driver: i915 v: kernel Display: x11 server: X.org v: 1.21.1.8 with: Xwayland v: 22.1.9 driver: X: loaded: modesetting,v4l dri: iris gpu: i915 resolution: 2560x1440~60Hz API: OpenGL v: 4.6 Mesa 24.1.4 renderer: Mesa Intel Graphics (ADL GT2) $ env LIBVA_DRIVER_NAME=i965
Created attachment 14634 [details] Crash log from launch of kodi The crash occurs at launch - no attempt to display interface.
Additional note relating to graphics configuration. xorg.conf contains: Section "Device" Identifier "device1" VendorName "Intel Corporation" BoardName "Intel Kernel Mode setting (Xorg modesetting)" Driver "modesetting" Option "DPMS" EndSection
Tried this again in Plasma. It failed for X11 but launched under Plasma Wayland. There is nothing much I can do in kodi so I exited after finding that a video database needed to be set up to play any local videos. $ kodi libva info: VA-API version 1.22.0 libva info: User environment variable requested driver 'i965' 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 So that issue is not fatal provided Wayland is being used. I also noticed that kodi had appeared in the list of desktop environments at login. Going to try that.
That was a dead end - a few screen clears then back to the sddm menu.
(In reply to Len Lawrence from comment #33) > Additional note relating to graphics configuration. > xorg.conf contains: > > Section "Device" > Identifier "device1" > VendorName "Intel Corporation" > BoardName "Intel Kernel Mode setting (Xorg modesetting)" > Driver "modesetting" > Option "DPMS" > EndSection Not sure if will change something but try add Option "AccelMethod" "glamor" before or after Option "DPMS" is equal BTW could you try before in terminal unset LIBVA_DRIVER_NAME and run kodi and looks what happen
@Len other thing you could try is rename ~/.kodi and see if by luck kodi works after that
With `unset LIBVA_DRIVER_NAME` the behaviour is the same. $ mv .kodi kodi $ kodi <crash> $ ls .kodi addons/ media/ system/ temp/ userdata/ $ ls -a .kodi/temp ./ ../ archive_cache/ kodi.log temp/ $ cd .kodi/temp $ less kodi.log [...] 2024-08-29 00:20:56.315 T:1129204 info <general>: VDPAU::Close - closing decoder context Modified /etc/X11/xorg.conf as suggested. Same result. $ tail kodi_crashlog-20240829_003324.log 2024-08-29 00:33:24.624 T:1229159 info <general>: VDPAU Decoder capabilities: 2024-08-29 00:33:24.624 T:1229159 info <general>: name level macbs width height 2024-08-29 00:33:24.624 T:1229159 info <general>: ------------------------------------ 2024-08-29 00:33:24.624 T:1229159 info <general>: Skipped 1 duplicate messages.. 2024-08-29 00:33:24.624 T:1229159 info <general>: VDPAU::Close - closing decoder context
@katnatek in reply to comment #36 My initial test was on an nvidia machine which is now defunct. This PC has Intel graphics. Shall try amdgpu next and apply your suggestions in sequence. Later.
mga9, x64 $ inxi -G Graphics: Device-1: AMD Lucienne driver: amdgpu v: kernel Device-2: PCTV Systems tripleStick 292e type: USB driver: em28xx Display: x11 server: X.org v: 1.21.1.8 with: Xwayland v: 22.1.9 driver: X: loaded: amdgpu,v4l dri: radeonsi gpu: amdgpu resolution: 2560x1440~60Hz API: OpenGL v: 4.6 Mesa 24.1.4 renderer: AMD Radeon Graphics (radeonsi renoir LLVM 15.0.6 DRM 3.54 6.6.37-desktop-1.mga9) Installed the update candidates. Mate desktop. LIBVA_DRIVER_NAME not set. Kodi works in that it launches cleanly and responds as expected. Did not take it very far. Ignored the request to set up a video library, viewed daily temperatures for Edinburgh and closed down. $ kodi libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 So, as expected, a change of graphical environment enables Kodi to run.
@Thomas, you view on this?, the issue that Len reports looks hardware specific. Should this be validated?
I had been waiting for this: "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." but it looks like that has been delayed indefinitely. I also have run into a problem with playing iptv with Kodi that wasn't there a couple of months ago. Nothing happened with the iptv-simple add-on, or Kodi, but now it says it can't play most of the channels it could before. I suspect some other update has broken the add-on. There's a newer version of the add-on, and for all I know it might fix it. But, that's something for a new bug. It would be nice if we could get an update from Stig on how close he is to 20.4.1-2, or if he's decided to skip that and go to Kodi 21. If the latter, again that would be a new bug.
(In reply to Thomas Andrews from comment #42) > I had been waiting for this: > > "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." > > but it looks like that has been delayed indefinitely. Not totally when Stig wrote that, the version to test was 20.4.1-1 and now we have 20.4.1-1.1, so something is changed but at this moment I can't check what could be as svnweb.mageia.org have issues > > I also have run into a problem with playing iptv with Kodi that wasn't there > a couple of months ago. Nothing happened with the iptv-simple add-on, or > Kodi, but now it says it can't play most of the channels it could before. I > suspect some other update has broken the add-on. There's a newer version of > the add-on, and for all I know it might fix it. But, that's something for a > new bug. > > It would be nice if we could get an update from Stig on how close he is to > 20.4.1-2, or if he's decided to skip that and go to Kodi 21. If the latter, > again that would be a new bug. I hope you other issues not depend on newer kodi because it is starting to be hard to build new things for mageia 9, perhaps Stig can try 20.5 that is the last of the 20 series
@Thomas I finally could see what changes from the previous to current packages and looks like is focus on wayland support
(In reply to katnatek from comment #43) > (In reply to Thomas Andrews from comment #42) > > I had been waiting for this: > > > > "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." > > > > but it looks like that has been delayed indefinitely. > > Not totally when Stig wrote that, the version to test was 20.4.1-1 and now > we have 20.4.1-1.1, so something is changed but at this moment I can't > check what could be as svnweb.mageia.org have issues > Actually, Stig mentioned in comment 6 that 20.4.1-1.1 (He had a typo, but I'm sure this is what he meant) would be pushed as soon as a couple of issues were worked out. That was before the 20.4.1-2 in comment 17. > > > > I also have run into a problem with playing iptv with Kodi that wasn't there > > a couple of months ago. Nothing happened with the iptv-simple add-on, or > > Kodi, but now it says it can't play most of the channels it could before. I > > suspect some other update has broken the add-on. There's a newer version of > > the add-on, and for all I know it might fix it. But, that's something for a > > new bug. > > > > It would be nice if we could get an update from Stig on how close he is to > > 20.4.1-2, or if he's decided to skip that and go to Kodi 21. If the latter, > > again that would be a new bug. > > I hope you other issues not depend on newer kodi because it is starting to > be hard to build new things for mageia 9, perhaps Stig can try 20.5 that is > the last of the 20 series I suspect that kodi-pvr-iptvsimple is the package that needs to be updated to fix my issue. But, keep in mind I am in no way a developer, and could easily be wrong.
(In reply to Thomas Andrews from comment #45) > (In reply to katnatek from comment #43) > > (In reply to Thomas Andrews from comment #42) > > > > > > I also have run into a problem with playing iptv with Kodi that wasn't there > > > a couple of months ago. Nothing happened with the iptv-simple add-on, or > > > Kodi, but now it says it can't play most of the channels it could before. I > > > suspect some other update has broken the add-on. There's a newer version of > > > the add-on, and for all I know it might fix it. But, that's something for a > > > new bug. > > > > > > It would be nice if we could get an update from Stig on how close he is to > > > 20.4.1-2, or if he's decided to skip that and go to Kodi 21. If the latter, > > > again that would be a new bug. > > > > I hope you other issues not depend on newer kodi because it is starting to > > be hard to build new things for mageia 9, perhaps Stig can try 20.5 that is > > the last of the 20 series > > I suspect that kodi-pvr-iptvsimple is the package that needs to be updated > to fix my issue. But, keep in mind I am in no way a developer, and could > easily be wrong. And it appears that indeed I was wrong. I had thought that the channels I was watching to test Kodi with iptv were legally free to view in the USA, but it would seem that Warner Brothers disagrees. They have taken steps that disable a LOT of iptv urls that worked just a month ago.
(In reply to katnatek from comment #41) > @Thomas, you view on this?, the issue that Len reports looks hardware > specific. > Should this be validated? It does look hardware specific, but Intel graphics is a major group of hardware. Len, I got lost in all your tests. Did you determine if the crashes are a new regression? And if not, does the wayland support katnatek mentioned make a difference? (Meaning, does it crash with X11, but not with Wayland?) If not a new regression, or if it works with X11 or Wayland but not the other, I suppose we could send it on, and let Stig work on it as he can.
(In reply to Thomas Andrews from comment #47) Not sure about new because I do not normally test kodi on a range of hardware. And the tests were usually under X11. It seems new to me. I shall check the Wayland||X11 situation tomorrow. If I make it through the night. The old ticker feels like it is about to go on strike. I am still not clear about Wayland versus X11. I always thought that Wayland was meant to be a complete replacement for X11. More research I guess.
@Thomas, @Len and others tester what do you think to try to convince to Wally who push 20.5 to cauldron to update also to that version for mageia 9? I build from the cauldron srpm and look that works, of course no warranty that the Len's issue go away
8-core AMD Ryzen 7 5700U with Radeon Graphics [MT MCP] Kodi works in Plasma. GNOME Classic on Wayland Display: wayland server: X.Org v: 22.1.9 with: Xwayland v: 22.1.9 compositor: gnome-shell v: 44.2 driver: X: loaded: amdgpu,v4l dri: radeonsi gpu: amdgpu resolution: 2560x1440~60Hz Kodi works, but: $ kodi libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 amdgpu: amdgpu_cs_ctx_create2 failed. (-13) Kodi from the sddm menu logs in to kodi. GNOME Classic on Xorg Display: x11 server: X.org v: 1.21.1.8 with: Xwayland v: 22.1.9 driver: X: loaded: amdgpu,v4l dri: radeonsi gpu: amdgpu resolution: 2560x1440~60Hz API: OpenGL v: 4.6 Mesa 24.1.4 renderer: AMD Radeon Graphics (radeonsi renoir LLVM 15.0.6 DRM 3.54 6.6.37-desktop-1.mga9) Kodi runs from a terminal. Tried Kodi with Mate on two other AMD machines and it launched successfully. So it is looking more likely that the fault is hardware-specific. Something about Intel?
(In reply to katnatek from comment #49) > @Thomas, @Len and others tester what do you think to try to convince to > Wally who push 20.5 to cauldron to update also to that version for mageia 9? > I build from the cauldron srpm and look that works, of course no warranty > that the Len's issue go away It's OK with me, but Stig is the one that needs to sign off on it. (In reply to Len Lawrence from comment #50) > Tried Kodi with Mate on two other AMD machines and it launched successfully. > So it is looking more likely that the fault is hardware-specific. Something > about Intel? Could be, could also be a certain Intel gpu. It looks to me like Kodi attempts to use hardware acceleration by default. Maybe something to do with that is the issue.
(In reply to Len Lawrence from comment #48) > I shall check the Wayland||X11 situation tomorrow. If I make it through the > night. The old ticker feels like it is about to go on strike. > Be sure to take care of yourself, Len. That is far more important than Kodi.
Thanks TJ. Some progress. Installed Mageia9 on a spare partition on the Intel machine, intending to upgrade to Cauldron to test the latest kodi but found that kodi now launches without any fuss. So the previous fault is not obviously hardware dependent. If nobody else is seeing problems then I would suggest let this go.
The news is not so good for Cauldron on an AMD machine where the mga9 version worked in Mageia9. Immediate crash. $ kodi libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 Fatal Python error: PyImport_AppendInittab: PyImport_AppendInittab() may not be called after Py_Initialize() Python runtime state: initialized Thread 0x00007f087dffb6c0 (most recent call first): <no Python frame> /usr/bin/kodi: line 181: 4474 Aborted (core dumped) ${KODI_BINARY} $SAVED_ARGS Not relevant to this bug but a possible headache for Stig. It could be my Mate environment of course. And, Cauldron is not complete yet.
They just did (or are still doing) a massive python update in Cauldron, according to the dev ML. Could be fallout from that, since the message cites a python error. (In reply to Len Lawrence from comment #53) > > Some progress. Installed Mageia9 on a spare partition on the Intel machine, > intending to upgrade to Cauldron to test the latest kodi but found that kodi > now launches without any fuss. So the previous fault is not obviously > hardware dependent. If nobody else is seeing problems then I would suggest > let this go. OK, thank you, Len. Now I wonder if your issue was from something left behind from a previous test of something else. But, as long as it works for your "problem" hardware on a known-to-be-clean MGA9 install... Validating. Katnatek, if Stig and Wally work out who is to do the next update, we'll use a new bug. BTW, according to https://kodi.wiki/view/Releases 21.1 became the latest stable version as of a few days ago.
CC: (none) => sysadmin-bugsWhiteboard: (none) => MGA9-64-OKKeywords: (none) => validated_update
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2024-0189.html
Status: NEW => RESOLVEDResolution: (none) => FIXED