From: Ian Eure <ian@retrospec.tv>
To: 67512@debbugs.gnu.org
Subject: [bug#67512] [PATCH 5/5] gnu: Add librewolf.
Date: Tue, 06 Feb 2024 15:29:22 -0800 [thread overview]
Message-ID: <874jekzzyl.fsf@retrospec.tv> (raw)
In-Reply-To: <w4s2lkqmwhnc5q4lalefo7gjuntimchux3za444qdbdr7vpmlh@3s4f5jrxfb77>
Herman Rimm <herman@rimm.ee> writes:
> On Sun, Jan 28, 2024 at 01:23:40PM -0800, Ian Eure wrote:
>>
>> Herman Rimm <herman@rimm.ee> writes:
>>
>> > Librewolf should not link to addons.mozilla.org, using this
>> > build phase
>> > from torbrowser:
>> >
>>
>> What’s the rationale for not using addons.mozilla.org?
>>
>> gnuzilla.gnu.org appears to be broken, it’s serving an Apache
>> default page,
>> as if the vhost isn’t configured. Does the browser request
>> some path within
>> that domain, which does work? I’m not familiar with the
>> mechanism used for
>> this.
>
> Apologies, the URL is: https://gnuzilla.gnu.org/mozzarella/. It
> is used
> because addons.mozilla.org contains nonfree extensions, from
> [1]:
>
I’ll look into this and see what it takes to adjust.
>>> LibreWolf disables DRM by default[1], so I don’t believe this
>>> flag is
>>> necessary. I can confirm that it’s disabled in the browser
>>> built from
>>> the package definition without this flag.
>>>
>>
>>I looked a bit deeper into this. There are actually no
>>EME-related
>>configuration options in Librewolf at all, either to enable or
>>disable it.
>>It’s always disabled.
>
> Interesting, I applied the patch series onto 551d013, built
> librewolf,
> removed ~/.librewolf and ~/.mozilla, started librewolf and went
> to
> about:config, where 'browser.eme.ui.enabled' has the default
> value
> 'true', so I can see and toggle the checkbox for 'play
> DRM-controlled
> content' in about:preferences. I don't know why
> 'browser.eme.ui.enabled'
> is 'true' by default for me, but I think adding --disable-eme
> will set
> the default to 'false', like it is in the icecat-minimal
> about:config.
>
I completely misunderstood the various settings and systems at
play here, which I believe led us to talk past each other. The
summary of the situation, best as I can tell, is this:
- EME support: a build setting controlling whether the browser
supports *any kind* of encrypted media playback.
- Widevine support: one kind of DRM, implemented as an EME plugin.
- `browser.eme.ui.enabled' browser preference: controls whether
the UI for DRM is visible. Controls visibility *only*. A
browser build without EME will still show this if
`browser.eme.ui.enabled' is `true' (but the control does
nothing). A browser build *with* EME (and one or more DRM
plugins) can have this set to `false' and still play DRM’d
content.
- The checkbox within the EME UI: On browsers built with EME and
DRM plugin(s), controls whether that is allowed to be used. On
browsers without EME+Widevine, does nothing.
The default configuration of a clean install of a stock LibreWolf
build is:
- The browser is built with EME and Widevine support
- The UI to enable DRM is visible.
- Within that UI, the checkbox is unchecked (meaning DRM is not
enabled).
I have rebuilt with --disable-eme and confirmed that even with
browser.eme.ui.enabled=true and the "Play DRM-controlled content"
box checked, the resulting build cannot play DRM’d streams. This
was actually somewhat difficult, since I don’t use or have access
to any commercial streaming service, but I found a website which
lets you test DRM playback, and used that to compare behavior of a
LibreWolf binary obtained from the project with my build. Should
anyone else want to verify, or need to do this kind of testing,
the site is: https://www.nuevodevel.com/nuevo/showcase/drm
> When running grep in a Librewolf repo [3] for the aformentioned
> terms,
> only the --disable-jxl configure flag is modified in toolkit/
> moz.configure, so I don't think the Librewolf developers disable
> EME.I
> am not sure though, I don't want to rebuild librewolf with the
> --disable-eme flag to look for the difference.
>
The "source" repo contains patches and orchestration to produce
the LibreWolf source tarball. The setting which disables DRM by
default is in their settings repo[1], which is a submodule. The
likely scenario is that you cloned the repo with the eminently
reasonable assumption that this would produce a full copy of its
contents, and grepped them. Unfortunately, Git submodules are
deeply unreasonable, and do not work this way -- you must perform
manual actions to populate or update them, which is very easy to
forget, especially if one doesn’t work with them regularly.
LibreWolf’s specific wording is "We disable DRM by default," which
I believe is accurate, but fails to capture the fullness of the
situation, i.e. that DRM support is included, but dormant. So
you’re also correct that they don’t disable EME -- the disabling
happens above that layer. This was not clear to me in the earlier
discussions.
I’ve removed EME from the build, and will work on replacing
Mozilla’s addons with Mozarella, then send an updated patch
series. Separately, I’ve also managed to unbundle libpng,
libwebp, and nss; fixed the glxinfo utility program; and
eliminated a redundant copy of the main binary.
Thanks,
— Ian
[1]:
https://gitlab.com/librewolf-community/settings/-/blob/ba238a9ca6bfd509f31e6eb4a45c14c11b7ef7fe/librewolf.cfg#L258-263
next prev parent reply other threads:[~2024-02-07 4:01 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 20:09 [bug#67512] [PATCH 0/5] Add LibreWolf Ian Eure
2023-11-28 20:13 ` [bug#67512] [PATCH 1/5] gnu: icu4c: Update to 73.1 Ian Eure
2023-11-28 20:13 ` [bug#67512] [PATCH 2/5] gnu: Add icu4c-71 Ian Eure
2023-11-28 20:13 ` [bug#67512] [PATCH 3/5] gnu: node: Switch to icu4c-71 Ian Eure
2023-11-28 20:13 ` [bug#67512] [PATCH 4/5] gnu: Add wasm packages Ian Eure
2023-11-28 20:13 ` [bug#67512] [PATCH 5/5] gnu: Add librewolf Ian Eure
2023-12-10 21:57 ` [bug#67512] [PATCH 0/5] Add LibreWolf Ludovic Courtès
2023-12-10 22:28 ` Ian Eure
2023-12-14 18:39 ` Ludovic Courtès
2024-01-13 17:53 ` [bug#67512] [PATCH 5/5] gnu: Add librewolf Herman Rimm via Guix-patches via
2024-01-28 21:23 ` Ian Eure
2024-01-28 22:51 ` Ian Eure
2024-02-02 18:44 ` Herman Rimm via Guix-patches via
2024-02-06 23:29 ` Ian Eure [this message]
2024-02-07 10:06 ` Clément Lassieur
2024-01-17 15:43 ` [bug#67512] [PATCH 0/5] Add LibreWolf Clément Lassieur
2024-02-17 16:06 ` Ian Eure
2024-02-11 19:20 ` [bug#67512] [PATCH v2 0/4] Add Librewolf Ian Eure
2024-02-11 20:22 ` Clément Lassieur
2024-02-11 23:23 ` Ian Eure
2024-02-11 23:32 ` Clément Lassieur
2024-02-11 19:20 ` [bug#67512] [PATCH v2 1/4] gnu: Move icu4c-73 from gnuzilla to icu4c Ian Eure
2024-02-11 21:40 ` Mark H Weaver
2024-02-11 22:14 ` Clément Lassieur
2024-02-11 23:23 ` Ian Eure
2024-02-11 23:34 ` Clément Lassieur
2024-02-11 19:20 ` [bug#67512] [PATCH v2 2/4] gnu: nss: Update to 3.97 Ian Eure
2024-02-11 19:20 ` [bug#67512] [PATCH v2 3/4] gnu: Add wasm packages Ian Eure
2024-02-11 19:20 ` [bug#67512] [PATCH v2 4/4] gnu: Add librewolf Ian Eure
2024-02-11 23:49 ` [bug#67512] [PATCH v3 1/4] gnu: Move icu4c-73 from gnuzilla to icu4c Ian Eure
2024-02-11 23:49 ` [bug#67512] [PATCH v3 2/4] gnu: nss: Update to 3.97 Ian Eure
2024-02-11 23:49 ` [bug#67512] [PATCH v3 3/4] gnu: Add wasm packages Ian Eure
2024-02-11 23:49 ` [bug#67512] [PATCH v3 4/4] gnu: Add librewolf Ian Eure
2024-02-13 20:34 ` [bug#67512] [PATCH v4 0/4] Add LibreWolf Ian Eure
2024-02-13 20:34 ` [bug#67512] [PATCH v4 1/4] gnu: Move icu4c-73 from gnuzilla to icu4c Ian Eure
2024-02-14 18:05 ` Mark H Weaver
2024-02-16 14:02 ` Clément Lassieur
2024-02-17 16:07 ` Ian Eure
2024-02-21 11:49 ` Clément Lassieur
2024-02-22 1:07 ` Ian Eure
2024-02-22 10:21 ` Clément Lassieur
2024-02-22 14:34 ` Mark H Weaver
2024-02-23 0:56 ` Ian Eure
2024-02-13 20:34 ` [bug#67512] [PATCH v4 2/4] gnu: nss: Update to 3.97 Ian Eure
2024-02-13 20:34 ` [bug#67512] [PATCH v4 3/4] gnu: Add wasm packages Ian Eure
2024-02-13 22:41 ` Liliana Marie Prikler
2024-02-13 23:22 ` Ian Eure
2024-02-16 14:29 ` Clément Lassieur
2024-02-16 21:48 ` Mark H Weaver
2024-02-17 16:09 ` Ian Eure
2024-02-21 2:00 ` Clément Lassieur
2024-02-21 2:18 ` Ian Eure
2024-02-21 5:20 ` Liliana Marie Prikler
2024-02-21 11:45 ` Clément Lassieur
2024-02-22 0:07 ` Ian Eure
2024-02-22 10:19 ` Clément Lassieur
2024-03-09 21:20 ` Ian Eure
2024-02-21 14:32 ` Mark H Weaver
2024-02-13 20:34 ` [bug#67512] [PATCH v4 4/4] gnu: Add librewolf Ian Eure
2024-02-25 0:53 ` [bug#67512] [PATCH v5 0/2] Add LibreWolf Ian Eure
2024-02-25 0:53 ` [bug#67512] [PATCH v5 1/2] gnu: nss: Update to 3.97 Ian Eure
2024-02-25 0:53 ` [bug#67512] [PATCH v5 2/2] gnu: Add librewolf Ian Eure
2024-03-13 9:07 ` [bug#67512] Feedback for Librewolf package Romain Garbage
2024-03-15 14:05 ` Ian Eure
2024-03-29 22:34 ` [bug#67512] [PATCH v6 0/2] Add LibreWolf Ian Eure
2024-03-29 22:34 ` [bug#67512] [PATCH v6 1/2] gnu: nss: Update to 3.98 Ian Eure
2024-03-29 22:34 ` [bug#67512] [PATCH v6 2/2] gnu: Add librewolf Ian Eure
2024-04-06 15:04 ` [bug#67512] [PATCH v7 0/3] Add LibreWolf Ian Eure
2024-04-06 15:04 ` [bug#67512] [PATCH v7 1/3] gnu: Add nss-3.98 Ian Eure
2024-04-06 15:04 ` [bug#67512] [PATCH v7 2/3] gnu: Add nss-certs-3.98 Ian Eure
2024-04-06 15:04 ` [bug#67512] [PATCH v7 3/3] gnu: Add librewolf Ian Eure
2024-04-12 13:11 ` bug#67512: [PATCH v7 0/3] Add LibreWolf Andrew Tropin via Guix-patches via
2024-04-27 10:46 ` [bug#67512] " Clément Lassieur
2024-04-27 17:19 ` bug#67512: " Ian Eure
2024-04-27 18:21 ` [bug#67512] " Ian Eure
2024-04-28 8:59 ` Clément Lassieur
2024-04-12 11:32 ` [bug#67512] [PATCH 0/5] " Sharlatan Hellseher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874jekzzyl.fsf@retrospec.tv \
--to=ian@retrospec.tv \
--cc=67512@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.