Blacklist Mesa in ESR17 (nothing sensational here --- ESR is the enterprise no-cool-stuff branch)

RESOLVED FIXED

Status

()

Core
Canvas: WebGL
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: bjacob, Assigned: bjacob)

Tracking

17 Branch
All
Linux
Points:
---

Firefox Tracking Flags

(firefox-esr1719+ verified)

Details

Attachments

(1 attachment)

In ESR10 Mesa was blacklisted and we've had many occasions to be thankful for that.

We should do the same for ESR17.

Example: bug 827106. I don't want to have to ask for ESR approval for a backport of this ANGLE patch.
(Assignee)

Comment 1

4 years ago
Created attachment 710465 [details] [diff] [review]
blacklist mesa in esr17
Attachment #710465 - Flags: review?(jgilbert)
Attachment #710465 - Flags: review?(jgilbert) → review+
(Assignee)

Comment 2

4 years ago
Comment on attachment 710465 [details] [diff] [review]
blacklist mesa in esr17

[Approval Request Comment]
If this is not a sec:{high,crit} bug, please state case for ESR consideration:
User impact if declined: see above. just a general protection measure, with bug 827106 as a good example of how it can be useful. just the continuation of what we've been doing on ESR10.
Fix Landed on Version: N/A
Risk to taking this patch (and alternatives if risky): we'll then have to do nontrivial backports to ESR17 for the next year as more Mesa bugs are found. See bug 827106 for instance.
String or UUID changes made by this patch: none
Attachment #710465 - Flags: approval-mozilla-esr17?
To be clear, the risks listed above are for if we *don't* take this patch. The patch itself is low risk. No risk if we can verify that WebGL is disabled on Mesa drivers but still enabled elsewhere.
(Assignee)

Comment 4

4 years ago
Oh, right, thanks. I should have added that under 'User impact if declined'. This patch is zero risk.

Updated

4 years ago
status-firefox-esr17: --- → affected
tracking-firefox-esr17: --- → 19+
Comment on attachment 710465 [details] [diff] [review]
blacklist mesa in esr17

PLease make sure to land before 2/11 .
Attachment #710465 - Flags: approval-mozilla-esr17? → approval-mozilla-esr17+

Updated

4 years ago
Assignee: nobody → bjacob
(Assignee)

Comment 6

4 years ago
https://hg.mozilla.org/releases/mozilla-esr17/rev/aa5ee636b118
status-firefox-esr17: affected → fixed
What needs to be tested here for Firefox 17.0.3esr? Is it just a matter of checking for something in about:support::Graphics?
Keywords: verifyme
(Assignee)

Comment 8

4 years ago
(In reply to Anthony Hughes, Mozilla QA (:ashughes) from comment #7)
> What needs to be tested here for Firefox 17.0.3esr? Is it just a matter of
> checking for something in about:support::Graphics?

Yes, that's a reliable way to do it. Ctrl+F WebGL, should say something like "not available" on Linux machines using Mesa drivers (i.e. anything not using proprietary drivers -- any default Ubuntu/Fedora will do).
Adapter Description: Tungsten Graphics, Inc -- Mesa DRI Intel(R) Ivybridge Desktop x86/MMX/SSE2
Vendor ID: Tungsten Graphics, Inc
Device ID: Mesa DRI Intel(R) Ivybridge Desktop x86/MMX/SSE2
Driver Version: 3.0 Mesa 8.0.4
WebGL Renderer: Blocked for your graphics driver version. Try updating your graphics driver to version Not Mesa or newer.

Verified fixed FF 17.0.3 ESR.
Not blocked in FF 17.0.2 ESR.
status-firefox-esr17: fixed → verified
OS: All → Linux
Given this is a branch-only bug (change request?) which has landed on that branch I'm going to call this FIXED. We weren't going to land this anywhere else, right?
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Version: Trunk → 17 Branch
mass remove verifyme requests greater than 4 months old
Keywords: verifyme
You need to log in before you can comment on or make changes to this bug.