[rolf@x570i ~]$ rpm -q kodi
kodi-18.6-1.mga7

I use kodi a lot, so thanks for this.  However, 18 won't play my iso video files.  They played in earlier versions.  I build kodi when packaged versions don't work well for my usage.  I have a binary "kodi-x11" from a build, "xbmc-18.0a2-Leia" that I compiled Jul 17  2018, apparently, and that works.  Later builds of 18 that I tried will not play my iso files.  

I moved my ~/.kodi directory and started kodi-18.6-1 to test.  After adding a video files source containing an iso I know to work before, I clicked that iso to play it.  For 5 or more minutes, there is a wait spinner and 2 of the 8 cores on this machine show 100% or more in htop.  I have to kill 9 to stop it.

A while back, I searched google on this issue, I thought I found a developer at kodi.tv forum advise to transcode the isos when someone else reported this new problem.  I can't find that, now, and perhaps I was mistaken.  Have you heard anything about this?

Thanks.

CC: (none) => rolfpedersen

(In reply to Rolf Pedersen from comment #1)
> [rolf@x570i ~]$ rpm -q kodi
> kodi-18.6-1.mga7
> 
> I use kodi a lot, so thanks for this.  However, 18 won't play my iso video
> files.  They played in earlier versions.  I build kodi when packaged
> versions don't work well for my usage.  I have a binary "kodi-x11" from a
> build, "xbmc-18.0a2-Leia" that I compiled Jul 17  2018, apparently, and that
> works.  Later builds of 18 that I tried will not play my iso files.  
> 
> I moved my ~/.kodi directory and started kodi-18.6-1 to test.  After adding
> a video files source containing an iso I know to work before, I clicked that
> iso to play it.  For 5 or more minutes, there is a wait spinner and 2 of the
> 8 cores on this machine show 100% or more in htop.  I have to kill 9 to stop
> it.
> 
> A while back, I searched google on this issue, I thought I found a developer
> at kodi.tv forum advise to transcode the isos when someone else reported
> this new problem.  I can't find that, now, and perhaps I was mistaken.  Have
> you heard anything about this?
> 
> Thanks.

I don't use ISO's, so can't tell right now.

Will investigate and get back to you as soon as I can.

Cheers,
Stig

I see that dvdcss is disabled in our build since it is in the tainted repo.

This means that if we want to enable it, we have to build Kodi as tainted as well.

Is this something we want to do?

Cheers,
Stig

(In reply to Stig-Ørjan Smelror from comment #3)
> I see that dvdcss is disabled in our build since it is in the tainted repo.
> 
> This means that if we want to enable it, we have to build Kodi as tainted as
> well.
> 
> Is this something we want to do?
> 
> Cheers,
> Stig

It's something *I* want to do. ;)  If I can go through the README.Linux at xbmc github one more time, figure out how to enable dvdcss (if that is what my kodi is lacking), and compile something that serves my relatively simple use habits, I'm good.

I don't believe playing isos (or dvds?) represents a vanishingly small component of Linux users and the feature might attract more Mageians.  I defer to the *we* who devote so much to Mageia to weigh and balance.

Thanks.

It's as simple as adding

-DENABLE_DVDCSS=ON

to cmake and make sure that lib(64)dvdcss-devel is installed.

Cheers,
Stig

I'm not a kodi user, so I don't have a horse in this race. That said, how about this as an idea?

We go ahead with Kodi 18 as is for an update for MGA7, assuming it works of course, then create and offer a tainted version as a backport. We could offer both in Cauldron, the same way as we do for VLC.

Would that be doable?

Rolf, would you be willing to test a backported Kodi for us to see if it solves your issue?

CC: (none) => andrewsfarm

(In reply to Thomas Andrews from comment #6)
...
> 
> Rolf, would you be willing to test a backported Kodi for us to see if it
> solves your issue?

Sure.

I've tried Kodi 18.6 in Mageia 7, works fine, plays video of various formats, music and images, I have been able to modify several things of the preferences, the folders of the libraries, etc. 

I don't use only kodi, I'm testing to get the upgrade going with the QA team. I will keep trying Kodi, but for the moment everything works ok.

Greetings!!

CC: (none) => joselp

Rolf, I have made a backport request for Kodi in Bug 26310. Please leave any comments you may have there, and we'll see how it goes.

Giving this an OK based on Jose's tests. Jose, for most updates, if you are satisfied with the results of your tests, you can give the OK yourself. Exceptions are for packages that need to be tested on a wide range of hardware, like kernels. For Mageia 7, just put either "MGA7-64-OK" or "MGA7-32_OK" or both, depending on which arch you did your testing.

Validating. Advisory in Comment 0.

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs
Whiteboard: (none) => MGA7-64-OK

Blast! Allowed myself to be distracted. Jose, to give an OK you put the notice in the Whiteboard, just as I did above.

(In reply to Thomas Andrews from comment #10)
> Blast! Allowed myself to be distracted. Jose, to give an OK you put the
> notice in the Whiteboard, just as I did above.

I don't understand, How do it?

(In reply to Jose Manuel López from comment #11)
> (In reply to Thomas Andrews from comment #10)
> > Blast! Allowed myself to be distracted. Jose, to give an OK you put the
> > notice in the Whiteboard, just as I did above.
> 
> I don't understand, How do it?

Just click on the white text field next to the word "Whiteboard" and type it in. It will be saved when you "Save Changes." If there is already an OK for another arch, add a space before your OK. Look at other bugs that have been given OKs for examples.

Ok, These fields do not appear to me now how editables in this bug, but I'll try to do that for future bugs.

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2020-0068.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED

(In reply to Jose Manuel López from comment #13)
> Ok, These fields do not appear to me now how editables in this bug, but I'll
> try to do that for future bugs.

Strange. They are editable for me. Well, this is not the place for this discussion. If you still have trouble in other bugs, ask on the QA ML and it will be investigated.