Widevide or widevine?

I don't know whether this helps:

https://support.mozilla.org/t5/Firefox/Firefox-fails-to-download-Widevine-CDM/td-p/1309637

Keywords: (none) => NEEDINFO
CC: (none) => marja11
Source RPM: (none) => firefox

Sorry Widevine :D :D

Thanks for the link.

Hi,

I couldÅt fix it with the info on the site you gave me.

This is what I did.

I downloaded Firefox 52.02 from Mozilla.org and ran it from Terminal.

I got to: https://demo.castlabs.com/

Played the Big Buck Bunny video with DRM and H264 and firefox installed the plugins in 2 seconds (This does not happen with the Mageia's Release)

Once I got back to Mageia's Firefox Release all plugins where installed correctly.

I can now even play Netflix, ClaroVideo (Latin America)

So, does it mean that there is something wrong with Mageia's Firefox Package?.

Regards

(In reply to Ezequiel Partida from comment #3)

> 
> I downloaded Firefox 52.02 from Mozilla.org and ran it from Terminal.
> 
> I got to: https://demo.castlabs.com/
> 
> Played the Big Buck Bunny video with DRM and H264 and firefox installed the
> plugins in 2 seconds (This does not happen with the Mageia's Release)
> 
> Once I got back to Mageia's Firefox Release all plugins where installed
> correctly.
> 
> I can now even play Netflix, ClaroVideo (Latin America)

Thanks for the feedback :-)
> 
> So, does it mean that there is something wrong with Mageia's Firefox
> Package?.


Sounds like it :-/

Assigning to all packagers collectively to investigate, since there is no registered Mageia maintainer for Firefox.

Summary: firefox is installing components needed to play the audio or video in this page. please try again later. => firefox-52.0.2-1.mga6 won't install widevine plugin (was: firefox is installing components needed to play the audio or video in this page. please try again later.)
Source RPM: firefox => firefox-52.0.2-1.mga6
Keywords: NEEDINFO => (none)
Assignee: bugsquad => pkg-bugs

Not just with widevine, the cisco openh264 plugin also fail to download/install

CC: (none) => j.alberto.vc

I just can confirm that with the mozilla's binary both plugins (widevine and cisco) download rigth and with magiea's version don't

Forgot to comment that my test was with  firefox-52.1.0-2, so this report is still valid

Still valid in  firefox-52.1.2-1.mga6.src.rpm

I backup all the gmp folders of my profile and then removed.
I can see the firefox create the folder gmp/Linux_x86-gcc3/ but not

gmp-gmpopenh264/1.6/ (and their content)
gmp-widevinecdm/1.4.8.903/ (and their content)


In about:addons you see that both plugins say will install later but that never happens

Summary: firefox-52.0.2-1.mga6 won't install widevine plugin (was: firefox is installing components needed to play the audio or video in this page. please try again later.) => Mageia's firefox 52 ESR won't install gmp plugins (widevine, openh264) (was: firefox is installing components needed to play the audio or video in this page. please try again later.)
Priority: Normal => High

1. The Mageia 6 firefox is able to play h264 html5 videos without problems. On all Live media the necessary gstreamer packages are included. - If you didn't install via LiveDVD, do: urpmi task-codec-video, and: urpmi task-codec-audio, maybe you would want to enable the tainted repos.

2. The DRM stuff is a different beast, and has nothing to do with playing h264 videos, the cisco openh264 and the widevine stuff is only about DRM, and this is disabled in the Mageia packages, as far as I can see, and with good reasons. If you want DRM (digital rights management), use either Firefox from the mozilla download or Google Chrome directly from Google.

'Some' settings in about:config -: (but maybe you need to add them, don't know, I do not and will never use DRM)

media.gmp-gmpopenh264.autoupdate
media.gmp-gmpopenh264.enabled
media.gmp-gmpopenh264.provider.enabled
media.peerconnection.video.h264_enabled

CC: (none) => shybluenight

(In reply to Chris B from comment #9)
1. I can't think in a good reason to make things more difficult to the user.
2. May be cisco's openh264 is not needed any more but in mageia 5 this plugin auto install, i'am sure at least this is don't related to DRM
3. Other packager (https://bugs.mageia.org/show_bug.cgi?id=17449#c9) is trying to give support to widevine for the chromium browser, i think this is the right way, let the user decide if he (or she) want the DRM, one don't activate the play DRM box by accident.
4. You can consider make a nonfree or tainted package of firefox to bring back this support if you are so worried by security or freedom.

Hi,

I installed Mageia 6 RC on a new fresh install on a new laptop and Firefox 52.2.0

I still get the next message:
firefox is installing components needed to play the audio or video in this page. please try again later.

It nevers get's out of it.

The first time I reported this it was fixed on the next release. It seems that the next updates where not fixed.

Regards
ZekeMX

(In reply to Ezequiel Partida from comment #11)
> Hi,
> 
> I installed Mageia 6 RC on a new fresh install on a new laptop and Firefox
> 52.2.0
> 
> I still get the next message:
> firefox is installing components needed to play the audio or video in this
> page. please try again later.
> 
> It nevers get's out of it.
> 
> The first time I reported this it was fixed on the next release. It seems
> that the next updates where not fixed.
> 
> Regards
> ZekeMX

I think the time it works was when you use mozilla's firefox and switch back to mageia's firefox.

Due comment #9 i think mageia's developers will close this as wontfix, so user that want to use netflix, clarovideo or any other using widevine will have to use mozilla's firefox.

For the moment if you try that use regular version instead of ESR, exists a bug that for the moment mozilla don't think is urgent to fix (https://bugzilla.mozilla.org/show_bug.cgi?id=1375708#c18)

This should be added to the errata with the documented workaround of comment 3 (i.e. download Mozilla's binary and use it to install the DRM plugins, then they work in Mageia's Firefox).

Keywords: (none) => FOR_ERRATA6

(In reply to Rémi Verschelde from comment #13)
> This should be added to the errata with the documented workaround of comment
> 3 (i.e. download Mozilla's binary and use it to install the DRM plugins,
> then they work in Mageia's Firefox).

Not for the moment, the upstream bug in my comment #12 make the DRM don't work with the ESR branch even if the gmp components are downloaded, i don't test is marked as solved in regular mozilla's firefox

Well I at least had a confirmation that this workaround works on Mageia 5 for Netflix.

(In reply to Rémi Verschelde from comment #15)
> Well I at least had a confirmation that this workaround works on Mageia 5
> for Netflix.

But was with a previous version of 52 ESR, the current 52.2.1 don't works for me, 
@Ezequiel Partida, can you try with current Mozilla's ESR https://www.mozilla.org/en-US/firefox/organizations/all/ ?

I confirm that with normal branch https://www.mozilla.org/en-US/firefox/all/ , i can use sites that require widevine DRM

But for use that branch you need

A)Create a new profile and run mozilla's firefox with -P option

or

B)Uninstall mageia's firefox and use ONLY mozilla's firefox

Don't know when mozilla's think to fix the bug of the comment #12 in the ESR branch.

The new update to firefox ESR (52.3) fix the issues with widevine
So when you publish the update to mageia's package the workarround of use mozilla's firefox to install gmp plugins should work again

Hi

I have the same problem with the openH264 codec video and plugin widevine. This problem concern only the firefox ESR version build by mageia. If I install the firefox ESR downloaded on the Mozilla Website, this problem is not present. 

The workaround is to download the ESR version of Mozilla to download the plugins, and then, once this is done, use the version produced by mageia.

This is annoying for beginners and this does not encourage using firefox.

CC: (none) => jeanmichel.varvou

Hello,

I do not understand the choice not to offer this functionality with the firefox version proposed by Mageia. Unless I'm mistaken, other linux distributions offer a version of firefox that allows the download of these plugins. Is this a technical problem? A problem related to the license of firefox?

(In reply to Chris B from comment #9)

> 2. The DRM stuff is a different beast, and has nothing to do with playing
> h264 videos, the cisco openh264 and the widevine stuff is only about DRM,
> and this is disabled in the Mageia packages, as far as I can see, and with
> good reasons.

Hi Chris, your comment there seems to trigger some people, or let's say they take this as explanation/reason that Mageia disabled widevine/DRM stuff on purpose.

Care to elaborate on what you are referring to as "disabled in the Mageia packages" and where you saw that in particular, please? I don't see anything related disabled on purpose here: http://svnweb.mageia.org/packages/cauldron/firefox/current/SPECS/firefox.spec?view=markup

CC: (none) => doktor5000

(In reply to Florian Hubold from comment #21)
> (In reply to Chris B from comment #9)
> 
> > 2. The DRM stuff is a different beast, and has nothing to do with playing
> > h264 videos, the cisco openh264 and the widevine stuff is only about DRM,
> > and this is disabled in the Mageia packages, as far as I can see, and with
> > good reasons.
> 
> Hi Chris, your comment there seems to trigger some people, or let's say they
> take this as explanation/reason that Mageia disabled widevine/DRM stuff on
> purpose.
> 
> Care to elaborate on what you are referring to as "disabled in the Mageia
> packages" and where you saw that in particular, please? I don't see anything
> related disabled on purpose here:
> http://svnweb.mageia.org/packages/cauldron/firefox/current/SPECS/firefox.
> spec?view=markup

I was not 100% sure back then if the packager of Firefox disabled the feature on purpose. I only checked Debian, and the same issue (same Firefox version) occured.
It could be indeed a firefox bug, or something in the spec file, but I'm too unexperienced to find the cause. 
Unfortunately our firefox has no assigned maintainer to ask.

FYI: downloading widevine lib for mageia's version of chromium-browser works fine for me, see bug 17449#c12

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=17449

The problem lies on the url used by mageia-branded firefox to retrieve the update.xml file containing the plugin links.
This url is built from the template in property media.gmp-manager.url:
"https://aus5.mozilla.org/update/3/GMP/%VERSION%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/%CHANNEL%/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/update.xml"

mageia FF renders it as
https://aus5.mozilla.org/update/3/GMP/52.5.0/20171114152041/Linux_x86_64-gcc3/null/esr52/Linux%204.9.56-desktop-1.mga6%20(GTK%203.22.16%2Clibpulse%2010.0.0)///update.xml
getting back an xml.file with only
<updates>
</updates>

while standard FF uses
https://aus5.mozilla.org/update/3/GMP/52.5.3/20171226003912/Linux_x86_64-gcc3/en-US/esr/Linux%204.9.56-desktop-1.mga6%20(GTK%203.22.16%2Clibpulse%2010.0.0)/default/default/update.xml
and obtains a filled xml:
<updates>
<addons>
<addon id="gmp-gmpopenh264" URL=long url and other data omitted />
<addon id="gmp-widevinecdm" URL=blah blah />
</addons>
</updates>

As you can see, there are four differences in the two urls, but the only ones that matter are the two /default/default/ at the end.
They refer to %DISTRIBUTION%/%DISTRIBUTION_VERSION% and mageia sets them to the empty string, while stock firefox uses "default"
BTW apparently you can use any string, not just "default", for example /mga6/mga6/ works, but you can't set them to blank

I suppose the two variables DISTRIBUTION and DISTRIBUTION_VERSION are set somewhere during the build but don't know where.
They seem to be related to about:config properties "distribution.id" and "distribution.version", both *missing* from stock firefox and set to the empty string in mageia's.

Setting both to default should fix the problem

CC: (none) => birrachiara

(In reply to R Ghetta from comment #24)

> As you can see, there are four differences in the two urls, but the only
> ones that matter are the two /default/default/ at the end.
> They refer to %DISTRIBUTION%/%DISTRIBUTION_VERSION% and mageia sets them to
> the empty string, while stock firefox uses "default"
> BTW apparently you can use any string, not just "default", for example
> /mga6/mga6/ works, but you can't set them to blank
> 
> I suppose the two variables DISTRIBUTION and DISTRIBUTION_VERSION are set
> somewhere during the build but don't know where.
> They seem to be related to about:config properties "distribution.id" and
> "distribution.version", both *missing* from stock firefox and set to the
> empty string in mageia's.
> 
> Setting both to default should fix the problem

Thanks for taking the time for that detailed analysis.

From a quick glance the build sets --with-distribution-id=org.mageia but then later writes %{mozillalibdir}/distribution/distribution.ini with empty values for 

> [Global]
> id=
> version=

which seems to overrule at least distribution-id during runtime.

Should be an easy fix.

Tested the fix in comment #24, updated the Mageia 6 Erratas

The current firefox 52.6.0-1.mga6 overwrite the file /usr/lib/firefox/distribution/distribution.ini (/usr/lib64/firefox/distribution/distribution.ini for 64 bit systems)

Is not issue if you already have the gmp plugins but if you create new profile (or new user) you have to repeat the fix,

Change the src.rpm because still valid for the most recent version

Source RPM: firefox-52.0.2-1.mga6 => firefox-52.6.0-1.mga6.src.rpm

Hi,
This is High priority bug for a good reason.

Making Mageia even better than ever is best direction.
In order to do right thing, this bug should be examined and fixed as soon as possible.

Packagers, please make the status to Assigned when you are working on this.
Feel free to reassign the bug if bad-triaged. Also, if bug is old, please close it.

On October 1st 2020, we will drop priority to normal.

I don't know why this bug is not closed, but as indicate in

https://wiki.mageia.org/en/Mageia_6_Errata#Firefox

This bug is solved time ago.


Feel free of reopend if you have some issue with current versions.

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