| Summary: | >=www-client/firefox-78.3.1 and >=mail-client/thunderbird-78.3.1: QA Notice: temp/environment: line 4534: mozconfig_annotate: command not found | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | tt_1 <herrtimson> |
| Component: | Current packages | Assignee: | Mozilla Gentoo Team <mozilla> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | sam |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
output from emerge --info
Firefox DRM warning |
||
|
Description
tt_1
2020-10-01 07:53:18 UTC
Created attachment 663409 [details]
output from emerge --info
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7c4062d8beed70792727317685707f42942415c9 commit 7c4062d8beed70792727317685707f42942415c9 Author: Thomas Deutschmann <whissi@gentoo.org> AuthorDate: 2020-10-01 11:39:59 +0000 Commit: Thomas Deutschmann <whissi@gentoo.org> CommitDate: 2020-10-01 11:43:12 +0000 mail-client/thunderbird: fix USE=eme-free Closes: https://bugs.gentoo.org/745930 Package-Manager: Portage-3.0.8, Repoman-3.0.1 Signed-off-by: Thomas Deutschmann <whissi@gentoo.org> mail-client/thunderbird/thunderbird-78.3.1.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7cf984de44717f414cb1977e0e00b5a2372b121e commit 7cf984de44717f414cb1977e0e00b5a2372b121e Author: Thomas Deutschmann <whissi@gentoo.org> AuthorDate: 2020-10-01 11:39:01 +0000 Commit: Thomas Deutschmann <whissi@gentoo.org> CommitDate: 2020-10-01 11:43:12 +0000 www-client/firefox: fix USE=eme-free Closes: https://bugs.gentoo.org/745930 Package-Manager: Portage-3.0.8, Repoman-3.0.1 Signed-off-by: Thomas Deutschmann <whissi@gentoo.org> www-client/firefox/firefox-78.3.1.ebuild | 2 +- www-client/firefox/firefox-81.0.1.ebuild | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) thanks for the fast fix I have USE=+eme-free , do I have to rebuild now? (In reply to tt_1 from comment #3) > I have USE=+eme-free , do I have to rebuild now? If want it to be effective then yes. Getting so many changes right now that I'd think better avoid revbumps for a bit. Created attachment 663469 [details] Firefox DRM warning Actually I believe that USE=eme-free is obsolete: The only available encrypted media extension is widevine at the moment (see https://github.com/Whissi/gentoo-mozilla/blob/firefox-esr-78.3.1/toolkit/moz.configure#L542-L594). So we will end up with MOZ_EME_MODULES being defined. This value is used in in https://github.com/Whissi/gentoo-mozilla/blob/firefox-esr-78.3.1/browser/moz.build#L47-L48 So we will end up with MOZ_WIDEVINE_EME being defined by default. This value is used in https://github.com/Whissi/gentoo-mozilla/blob/firefox-esr-78.3.1/browser/app/profile/firefox.js#L182-L186 But this will only trigger attached DRM warning notification in Firefox. > I have USE=+eme-free , do I have to rebuild now? So no, you don't need to rebuild. If you don't want to see this notification when you hit DRM content, manually set "browser.eme.ui.enabled" to "false". And why do I believe this option is obsolete? Because it's just a notification and it is good to tell user "This page shouldn't be empty/white but I need DRM to show something". Widevine itself is delivered via Gecko Media Plugin (gmp-widevinecdm), i.e. firefox will try to download the required lib by default on first usage (after you will give permission) and store it in user's profile (for amd64 it's currently https://redirector.gvt1.com/edgedl/widevine-cdm/4.10.1582.2-linux-x64.zip as set in https://github.com/Whissi/gentoo-mozilla/blob/firefox-esr-78.3.1/toolkit/content/gmp-sources/widevinecdm.json#L16-L20). That is getting controlled via USE=gmp-autoupdate which is enabled by default because we want users to receive updates. Notice: Another popular GMP is the h264 plugin provided by CISCO to allow firefox to play h264 content (gmp-gmpopenh264). However, we have USE=openh264 enabled by default which will pull in media-libs/openh264[plugin] (should be the same like binary blob but build on your own). When openh264 is already present, firefox will use system lib instead and will *not* download any blob. However, the blob is stored in user's profile. So once it was downloaded and is present in profile, Firefox will keep using that blob despite the fact that you installed openh264 in the meanwhile. That's why we have auto-enabled USE=gmp-autoupdate to ensure that old installations will receive updated h264 plugin... I find it rather confusing as well, there's an older bug with more informations on what --enable-eme actually does and how it lately changed: https://bugzilla.mozilla.org/show_bug.cgi?id=1528884 these informations are for the old 68-esr, but yes the issue of not wanting any of the binary blobs landing in users profile should be solved by setting the value via all-gentoo.js, or whatever that file is called where the so called sensible defaults for new profiles are provided. |
