Craig, that is a different problem, tracked by
https://bugzilla.mozilla.org/show_bug.cgi?id=1732580, and fixed in the
upcoming Firefox 94 (currently in the beta channel).
** Bug watch added: Mozilla Bugzilla #1732580
https://bugzilla.mozilla.org/show_bug.cgi?id=1732580
** Changed in: firefox
I upgraded my PC from 21.04 to 21.10. I found that WebGL doesn't work in
the snap firefox that 21.10 installed.
I uninstalled the snap firefox and installed the deb firefox via apt.
That fixed the WebGL issue.
--
You received this bug notification because you are a member of Desktop
Packages,
Reproduced the issue on Firefox 83.0 under Ubuntu 20.04 and Windows 7 by
verifying google maps and low performance from the link found in Comment
23.
The 3D map works, and the performance is good for the link found in
Comment 23 on Nightly 87.0a1 (2021-02-03) and Firefox 86.0b5 under
Ubuntu 20.04
Is this something we should consider uplifting to Beta for 85?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1905054
Title:
Firefox 83 Breaks WebGL
Status in Mozilla Firefox:
Fix
(In reply to panzi from comment #22)
> > Call these bad websites, and try outreach/education
>
> How do I call Google? Also since they haven't fixed it until now, I doubt
> they ever will. Is there some hack to make it work? An user script?
That was supposed to be "call out", sorry!
Google Maps
Created attachment 9194895
Bug 1678652 - Disable failIfMajorPerformanceCaveat by default.
The goal of the WebGL Working Group was for failIfMajorPerformanceCaveat
to allow websites to make better choices about which content to serve to
users, ideally via offering a choice to users.
I no longer
Pushed by jgilb...@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/bb634a5d7268
Disable failIfMajorPerformanceCaveat by default. r=lsalzman
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
The goal of the WebGL Working Group was for failIfMajorPerformanceCaveat
to allow websites to make better choices about which content to serve to
users, ideally via offering a choice to users.
I no longer think that this is useful here, or rather it's only ever
useful in the very narrow case:
https://hg.mozilla.org/mozilla-central/rev/bb634a5d7268
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1905054
Title:
Firefox 83 Breaks WebGL
Status in Mozilla Firefox:
Fix
*** Bug 1684475 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1905054
Title:
Firefox 83 Breaks WebGL
Status in Mozilla Firefox:
Same problem on a Lenovo T530, i915 grafic controller, using via Firefox 84.0
(Ubuntur 20.04.1 LTS) tensorflow e.g with
https://storage.googleapis.com/tfjs-models/demos/posenet/camera.html
Just by calling the page it tells (along with poor peformance):
Failed to create WebGL context:
(In reply to Jeff Gilbert [:jgilbert] from comment #24)
> (In reply to Pat Suwalski from comment #20)
> > (In reply to Jeff Gilbert [:jgilbert] from comment #19)
> > > Honestly at this point I'm tending towards #2.
> > > Websites had the chance to handle this well and they have bungled it, so
> >
(In reply to Jeff Gilbert [:jgilbert] from comment #25)
> (In reply to panzi from comment #22)
> > > Call these bad websites, and try outreach/education
> >
> > How do I call Google? Also since they haven't fixed it until now, I doubt
> > they ever will. Is there some hack to make it work? An
I can't speak for 3D, but seeing as the 2D rendering is still loads
quicker than canvas, the "performance caveat" really isn't.
What should PIXI, or any site, do with this information?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Since the status are different for nightly and release, what's the status for
beta?
For more information, please visit [auto_nag
documentation](https://wiki.mozilla.org/Release_Management/autonag#missing_beta_status.py).
--
You received this bug notification because you are a member of Desktop
The system unfortunately does (probably) have a performance caveat,
because we've included "readback required for compositing" as a caveat,
which is a long-time issue on Linux for us.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
(In reply to Pat Suwalski from comment #20)
> (In reply to Jeff Gilbert [:jgilbert] from comment #19)
> > Honestly at this point I'm tending towards #2.
> > Websites had the chance to handle this well and they have bungled it, so I
> > think we should disable failIfMajorPerformanceCaveat as it
** Changed in: firefox
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1905054
Title:
Firefox 83 Breaks WebGL
Status in Mozilla Firefox:
> Call these bad websites, and try outreach/education
How do I call Google? Also since they haven't fixed it until now, I
doubt they ever will. Is there some hack to make it work? An user
script?
--
You received this bug notification because you are a member of Desktop
Packages, which is
(In reply to Jeff Gilbert [:jgilbert] from comment #18)
> After bug 1680595, it should be more clear to (power) users what they can do
> to mitigate this.
>
> Functionality here is, I think, working as intended now. Unfortunately the
> specified behavior causes certain websites (which arguably
** Changed in: firefox
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1905054
Title:
Firefox 83 Breaks WebGL
Status in Mozilla Firefox:
Confirmed
Honestly at this point I'm tending towards #2.
Websites had the chance to handle this well and they have bungled it, so I
think we should disable failIfMajorPerformanceCaveat as it stands today.
--
You received this bug notification because you are a member of Desktop
Packages, which is
(In reply to Jeff Gilbert [:jgilbert] from comment #19)
> Honestly at this point I'm tending towards #2.
> Websites had the chance to handle this well and they have bungled it, so I
> think we should disable failIfMajorPerformanceCaveat as it stands today.
Are you suggesting PIXI doesn't handle
Although Firefox 84b2 from official binaries worked fine, Firefox 84.0
from official binaries (firefox-84.0.tar.bz2) does not.
Setting ```gfx.webrender.all``` as suggested above *does* work.
This appears to be a capability detection issue.
--
You received this bug notification because you are
After bug 1680595, it should be more clear to (power) users what they
can do to mitigate this.
Functionality here is, I think, working as intended now. Unfortunately
the specified behavior causes certain websites (which arguably may have
made poor choices) work worse for our users, whereas before
I don't know if Google Maps changed something, but after setting
`gfx.webrender.all` to true and restarting Firefox 83, I do get 3D
satellite maps.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
Setting gfx.webrender.all as recommended in the upstream bug makes it
work. It seems some detection code is broken.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1905054
Title:
Can anyone point me to where I can find the Firefox 82 debs? They seem
to have disappeared from /var/cache/apt/archives, and I really need
them.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
The Firefox 84 WebGL section looks a lot like the v83 section:
HW_COMPOSITING
available by default
blocked by env: Acceleration blocked by platform
OPENGL_COMPOSITING
unavailable by default: Hardware compositing is disabled
WEBRENDER
available by default
disabled by env: Not
Despite it working in The Firefox 84 beta, the Ubuntu build that came
out does not work.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1905054
Title:
Firefox 83 Breaks WebGL
Status
** Bug watch added: Mozilla Bugzilla #1679610
https://bugzilla.mozilla.org/show_bug.cgi?id=1679610
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1905054
Title:
Firefox 83 Breaks
*** Bug 1679610 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1905054
Title:
Firefox 83 Breaks WebGL
Status in Mozilla Firefox:
The severity field is not set for this bug.
:jgilbert, could you have a look please?
For more information, please visit [auto_nag
documentation](https://wiki.mozilla.org/Release_Management/autonag#workflow.2Fno_severity.py).
--
You received this bug notification because you are a member of
(In reply to Jeff Gilbert [:jgilbert] from comment #12)
> (In reply to michaelspohn from comment #8)
> > (In reply to michaelspohn from comment #7)
> > > (In reply to Pat Suwalski from comment #6)
> > > > Can you guys try the Firefox 84b2 build? I tried it from the tarball
> > > > and it worked
(In reply to michaelspohn from comment #8)
> (In reply to michaelspohn from comment #7)
> > (In reply to Pat Suwalski from comment #6)
> > > Can you guys try the Firefox 84b2 build? I tried it from the tarball and
> > > it worked perfectly.
> >
> > No change, still broken on Windows 10...
>
>
The severity field is not set for this bug.
:jgilbert, could you have a look please?
For more information, please visit [auto_nag
documentation](https://wiki.mozilla.org/Release_Management/autonag#workflow.2Fno_severity.py).
--
You received this bug notification because you are a member of
Could you open about:support, click the "Copy text to clipboard" button,
come back to this bug, click the "Attach New File" button above, and
paste into the "File:" box and submit that troubleshooting information,
please.
--
You received this bug notification because you are a member of Desktop
Same problem happens under Windows 10 (1909) with an AMD Radeon HD 6450
graphics card.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1905054
Title:
Firefox 83 Breaks WebGL
Status
Same problem for me with Firefox 83.0 (64bit) under Fedora Linux, using the
official Firefox from the Mozilla website, when trying to load the 3D view of
Google Maps. Have to use Google Chrome for that now. :(
Graphics Card: GeForce GTX 760
NVIDIA Driver Version: 455.38
--
You received this
Can you guys try the Firefox 84b2 build? I tried it from the tarball and
it worked perfectly.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1905054
Title:
Firefox 83 Breaks WebGL
Created attachment 9190103
Attached about:config per instructions
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1905054
Title:
Firefox 83 Breaks WebGL
Status in Mozilla Firefox:
(In reply to michaelspohn from comment #7)
> (In reply to Pat Suwalski from comment #6)
> > Can you guys try the Firefox 84b2 build? I tried it from the tarball and it
> > worked perfectly.
>
> No change, still broken on Windows 10...
Fun fact: Chrome 87.0.4280.66 and Edge 87.0.664.47 also do
(In reply to Pat Suwalski from comment #6)
> Can you guys try the Firefox 84b2 build? I tried it from the tarball and it
> worked perfectly.
No change, still broken on Windows 10...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Alright, let's mark as fix commited, it's not likely we will try to
figure out what patches to backport and do another round of updates for
that fix before the new version is out so that will likely wait for the
next upload
> but I thought you said in comment #2 that is a binary build straight
If I were to speculate, someone tried to fix the "blocked by env" errors
in Firefox 82, in the process actually making that statement true with
some kind of fail code. In 84 they may have actually fixed whatever the
root problem reporting that message.
--
You received this bug notification
I can verify that the beta snap works as well, but I thought you said in
comment #2 that is a binary build straight from mozilla.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1905054
To rule out again the packaging format, does it work or not with the new
version from the snap ('sudo snap refresh --beta firefox)?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
Launchpad has imported 4 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1678652.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
It's the "Acceleration blocked by platform" bits that are interesting.
It seems that message is there in v82 where it works and v83 where it
doesn't. The apparmor check seems relevant with that angle, I just want
to make sure that it's not something related to Ubuntu.
If it continues to work in
I just realized that the about:support output above is actually for
Firefox 82, which is odd, because it does work even though the output
suggests it shouldn't.
Here's a lot for Firefox 83.
The relevant section is different once again:
Decision Log
HW_COMPOSITING:
available by default
blocked
Thanks for the details Pat. Not sure what is going on, but it is good to
know that this is fixed in the upcoming firefox 84. Let's see if
upstream can shed some light on the problem in the bug report you filed
there.
--
You received this bug notification because you are a member of Desktop
I just realized that the about:support output I supplied above is from
firefox 82. I am confused by the HW_COMPOSITING section, when it clearly
works in v82.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
Indeed, I downloaded firefox-84.0b4.tar.bz2 and WebGL works correctly in
that build.
On 84, compared to 83 above:
Decision Log
HW_COMPOSITING
available by default
OPENGL_COMPOSITING
available by default
WEBRENDER
available by default
WEBRENDER_QUALIFIED
available by default
Here is the output of about:support. I suspect this is the relevant
part:
Decision Log
HW_COMPOSITING:
available by default
blocked by env: Acceleration blocked by platform
OPENGL_COMPOSITING:
unavailable by default: Hardware compositing is disabled
WEBRENDER:
opt-in by default: WebRender is an
It happens to me too (AMD Renoir) but the interesting bit is that
Firefox 84 (developer preview) works.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1905054
Title:
Firefox 83
This has been reported separately here: https://discourse.mozilla.org/t
/webgl-context-errors-in-firefox-83/70924 (although for different HW
configurations).
Are you running firefox with apparmor confinement? (check the output of
`sudo apparmor_status`).
Can you open about:support and share the
Thanks for testing and commenting upstream, indeed I meant xorg in the
previous comment.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1905054
Title:
Firefox 83 Breaks WebGL
Status
Thanks for the ideas.
drm driver as listed from lsmod:
drm 491520 9 drm_kms_helper,i915
I tried the snap and it behaved the same way, the exact same console
output. The snap was version 83.0-2 via snapcraft.io.
I assume by "xrg" you mean "xorg"? I have not tried under an xorg
Thank you for your bug report. What videocard and driver do you use?
Could you perhaps try if the firefox snap has the same issue? That's a binary
build from mozilla so it would help to figure if it's an upstream or packaging
issue
Did you try under an xrg session?
--
You received this bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: firefox (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
Public bug reported:
Upon upgrading from Firefox 82 to to Firefox 83, WebGL stops working.
Ubuntu 20.10 with Wayland.
When I try to launch a webGL game:
Failed to create WebGL context: failIfMajorPerformanceCaveat: Compositor is not
hardware-accelerated.
Specifically Pixi says:
Error: WebGL
61 matches
Mail list logo
