Mageia forum

Having recently been accorded the privilege of fast broadband, I thought to avail myself of video streaming from Amazon Prime. However Firefox indicates that this cannot take place until a plugin "Widevine Content Decryption Module provided by Google" is installed. All very well, so far, but a notification that this will be installed "shortly" in Firefoxes header, seems to be referring to shortly in geological terms. The notification has been there for a week and nothing is happening. Has anyone any idea what is going on, or perhaps not going on. This problem exists in all systems of Mageia, both Mga 5 and 6

That is mostly covered via the errata: https://wiki.mageia.org/en/Mageia_6_Err ... ot_working

Thanks, Doktor, that fixed ther problem, at a stroke. I was not aware that Mageia 'crippled' applications in the repositories, in any way. Is there anywhere that I can read up on this, to my mind, rather strange practice? I'll consider the thread closed, in the usual way.

Well, Mageia does not "cripple" applications.
From what I can see, DRM is not explicitly disabled regarding firefox. You are welcome to find out why widevine does not work with the firefox version from the Mageia repositories and submit a patch to make it work.

It is not that Widevine does not work, It's that Mageia will not allow widevine to be installed, as far as I can see (On security issues according to your errata link). However a work around is a solution so I shall stick with that.

rodgoslin wrote:It is not that Widevine does not work, It's that Mageia will not allow widevine to be installed, as far as I can see

There is nothing explicitly "not allowing" widevine to install that was put in place purposely by Mageia. I'll also repeat again:

You are welcome to find out why widevine does not work with the firefox version from the Mageia repositories and submit a patch to make it work.

And that "due security motives" in the errata was misleading, I can't see that anywhere in the cited bugreport, hence I've removed it now.

Well, where does it say anything about "security motives" ?
(and looking at the spec for firefox, I can't see DRM being explicitly disabled, either - feel free to point out where this is being disabled, check http://svnweb.mageia.org/packages/cauld ... iew=markup )

Well i see security as the motive before, i remember a discuss with the Russian community about a Mageia patch that disable some feature of hplip.

But maybe this time is a monetary or license issues, in the build of arch exist
a goolgle api key that not exist in mageia's build.

May be my original claim about security issues was wrong but packagers don't give information

katnatek wrote:May be my original claim about security issues was wrong but packagers don't give information

What do you mean "packagers don't give information"? I've just pointed out the spec for firefox to you, that's basically all there is to our firefox package. What more infomation do you expect ?

In the bug report, just the comment i previously link.
But no other confirm or give alternative explanation.

Users could understand if is by license or monetary or security or
even like in the case of cdrtool because nobody wants to implement,
but what is not understandable is lack of information.

katnatek wrote:In the bug report, just the comment i previously link.
But no other confirm or give alternative explanation.

Well, you just ignored my explanation / confirmation ?

katnatek wrote:Users could understand if is by license or monetary or security
[...]
but what is not understandable is lack of information.

You're way off there. I'll repeat again, just for you:

There is nothing explicitly "not allowing" widevine to install that was put in place purposely by Mageia. I'll also repeat again:

You are welcome to find out why widevine does not work with the firefox version from the Mageia repositories and submit a patch to make it work.

I've commented in the bugreport to try to clarify this.

doktor5000 wrote:Well, you just ignored my explanation / confirmation ?

Of course not, i even point to you in other comment to a detail in arch linux build (https://aur.archlinux.org/cgit/aur.git/ ... irefox-esr),
but i can't check for other distributions.

katnatek wrote:Users could understand if is by license or monetary or security
[...]
but what is not understandable is lack of information.

[/quote]

doktor5000 wrote:You're way off there. I'll repeat again, just for you:

The spec file always have technical but no political issues, also have
information about what do, just in some cases what don't do and why (to be clear i'm not saying this is the case).
I sorry if my explanations are not much detailed, but is a few hard to me
write my ideas in english, but please don't take my words as attack.

doktor5000 wrote:There is nothing explicitly "not allowing" widevine to install that was put in place purposely by Mageia. I'll also repeat again:
You are welcome to find out why widevine does not work with the firefox version from the Mageia repositories and submit a patch to make it work.
I've commented in the bugreport to try to clarify this.

I apologize once more time to put wrong information in the Errata. I don't have time to search why is failing in Mageia, i put the errarta just because some one found this issue, and in my experience once this kind of issues rise once they repeat from time in time, i thank you for your time trying to bring light to this.

katnatek wrote:Of course not, i even point to you in other comment to a detail in arch linux build (https://aur.archlinux.org/cgit/aur.git/ ... irefox-esr), but i can't check for other distributions.

So you're saying that the google API key reproducibly will allow widevine to install, did you test that out? Or is that just a wild guess?

katnatek wrote:I apologize once more time to put wrong information in the Errata. I don't have time to search why is failing in Mageia, i put the errarta just because some one found this issue, and in my experience once this kind of issues rise once they repeat from time in time, i thank you for your time trying to bring light to this.

You do not need to apologise, it was clearly out of good intent and the errata entry itself is helpful.

It's just that this can lead to others asking (like in the recent comments in the bugreports) "why is Mageia not allowing widevine ..." or "what security motives ..."
That was my point.

doktor5000 wrote:So you're saying that the google API key reproducibly will allow widevine to install, did you test that out? Or is that just a wild guess?

Just Guessing, widevine is part of google, but as long as i don't check other builds and by architecture limitations can't test Arch, i can't be 100% sure.

doktor5000 wrote:It's just that this can lead to others asking (like in the recent comments in the bugreports) "why is Mageia not allowing widevine ..." or "what security motives ..."
That was my point.

Of course, i understand that, i will be more careful next time