User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:99.0) Gecko/20100101 Firefox/99.0

Steps to reproduce:

I get this error on my about:support tab:

Failure Log
(#0) Error No GPUs detected via PCI
(#1) Error glxtest: process failed (received signal 11)

and as a result (probably because of it) i have no working webgl.

WebGL 2 Driver Renderer Intel -- Mesa Intel(R) Xe Graphics (TGL GT2)
WebGL 2 Driver Version 4.6 (Core Profile) Mesa 22.0.1

Linux, Arch, Xwayland, mesa 22. using enlightenment as a desktop.

I noticed this with the 99 version of FF

Actual results:

No working webgl

Expected results:

Have working webgl

The Bugbug bot thinks this bug should belong to the 'Core::Graphics' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

I have the same problem running firefox beta on new ubuntu 22.04 installation when forcing use of wayland on firefox.

The severity field is not set for this bug.
:bhood, could you have a look please?

For more information, please visit auto_nag documentation.

Please attach the output of your about:support to this bug.

the requested file.

Jeff, have you seen this behavior before?

Same behavior on FF 100 also.

If this is a regression can you find a regression window using mozregression?

(In reply to Jeff Muizelaar [:jrmuizel] from comment #8)

If this is a regression can you find a regression window using mozregression?

I am using normal releases. WebGL worked on 98 and it doesn't work on 99 and 100.

Ok, good. Please find a regression window.

Do you have pciutils installed and no AppArmor rule that blocks it?

Please try to find a regression range, you get a pushlog url at the end:
$ pip3 install --user --upgrade mozregression
$ ~/.local/bin/mozregression --good 98 --bad 99 -a https://webglsamples.org/aquarium/aquarium.html

OK. The problem seems to be how the distro builds the package since the runs that mozregression downladed worked fine. Its weird however because arch always follows upstream in the way it does things.

BTW when i run the aquarium normally i get:
Status: WebGL creation failed: * tryNativeGL () * Exhausted GL driver options. (FEATURE_FAILURE_WEBGL_EXHAUSTED_DRIVERS)

Nightly uses Wayland by default, you could try this to force Xwayland:
$ MOZ_ENABLE_WAYLAND=0 ~/.local/bin/mozregression --good 98 --bad 99 -a https://webglsamples.org/aquarium/aquarium.html

Wayland or Xwayland i get the same result on the normal arch build. WebGL doesn't work.

Coming back to this since i faced the same issue on weston. There however i went into about:config and reset all values that had "FEATURE_FAILURE_GLXTEST_FAILED" in them and restarted firefox. It worked after that on weston.

No idea what causes those values on some of the options in about:config.

I'm experiencing the same issue on Sway + Nvidia

Also on Arch Linux with everything on latest.

I tried the bisect command as follows:

$ ~/.local/bin/mozregression --profile .mozregprof --profile-persistence clone-first --good 98 --bad 99 -a https://webglsamples.org/aquarium/aquarium.html

Since I'm on Nvidia to manually force enable webrender and webgl in about:config.

Results are followed:

8:01.24 INFO: Last good revision: d6aabaf771d4c6ee0a63b24e79b3afe379ce7bd6
8:01.24 INFO: First bad revision: 1edd1e4056e62592fe5f457926e5012ad30003d6
8:01.24 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=d6aabaf771d4c6ee0a63b24e79b3afe379ce7bd6&tochange=1edd1e4056e62592fe5f457926e5012ad30003d6

Actually looking at 1edd1e4056e62592fe5f457926e5012ad30003d6

One could just change security.sandbox.content.headless to false to get WebGL working again as a temporary solution.

There's still the problem with VAAPI (using https://github.com/elFarto/nvidia-vaapi-driver/) however,

Which remains

failed by runtime: Failed to configure

The same configuration works in KDE/GNOME

glxtest crashes here:

https://searchfox.org/mozilla-central/source/toolkit/xre/glxtest.cpp#933

Specifically at wl_display_roundtrip(dpy);

Not sure if this is a Sway issue or an NVIDIA issue... (or maybe wlroots?)

Based on comment #16, this bug contains a bisection range found by mozregression. However, the Regressed by field is still not filled.

:jld, since you are the author of the changes in the range, if possible, could you fill the Regressed by field and investigate this regression?

For more information, please visit auto_nag documentation.

me too... 102.7.0 (64-bit)

LANG=EN; thunderbird &
[1] 2171943
elias@eliasc:~$ [Parent 2171943, Unnamed thread 7f2649e25dc0] WARNING: Failed to set scheduler settings: Η λειτουργία δεν επιτρέπεται: 'glib warning', file /builds/worker/checkouts/gecko/toolkit/xre/nsSigHandlers.cpp:167

(thunderbird:2171943): GLib-CRITICAL **: 15:08:38.406: Failed to set scheduler settings: Η λειτουργία δεν επιτρέπεται
[GFX1-]: No GPUs detected via PCI
[GFX1-]: glxtest: process failed (received signal 11)
Exiting due to channel error.
Exiting due to channel error.

,g$$$$$$$$$$$$$$$P.       ------------ 

,g$$P" """Y$$.". OS: Debian GNU/Linux 11 (bullseye) x86_64
,$$P' $$$. Host: B85M-HD3 R4 ',$$P ,ggs.$$b: Kernel: 5.11.0-18-generic
d$$' ,$P"' . $$$ Uptime: 28 days, 3 hours, 16 mins $$P d$' , $$P Packages: 6834 (dpkg), 9 (flatpak) $$: $$. - ,d$$' Shell: bash 5.1.4 $$; Y$b._ _,d$P' Resolution: 1920x1080 Y$$.."Y$$$$P"' DE: Plasma 5.21.4$$b "-.__ WM: KWin
Y$$ Theme: Breeze Light [Plasma], Breeze [GTK2], Adwaita [GTK3]Y$$. Icons: breeze [Plasma], breeze [GTK2/3]
$$b. Terminal: lxterminalY$$b. Terminal Font: Monospace 10
"Y$b._ CPU: Intel i5-4570S (4) @ 3.600GHz""" GPU: NVIDIA GeForce GT 1030
Memory: 8176MiB / 15961MiB

(ver102.7.0 on debian bullseye11 with x11) BUT chrt -o 0 thunderbird seems to solve the problem, for now (not tested excessively). Note that in KsysGuard i had changed nice and ionice values to higher priority, and i cannot change them back. :) Found solution from here (firefox): https://bugzilla.mozilla.org/show_bug.cgi?id=1689207

If you're using egl-wayland, then I have some updates. See comment 25 of #1759315

NVIDIA/egl-wayland#74 fixes glxtest SIGSEGV'ing (i.e. glxtest: process failed (received signal 11), thus causing No GPUs detected via PCI).

Unfortunately, the latest release, 1.1.11, still doesn't feature the fix.
You have three options:

• on Arch Linux, the egl-wayland package is already patched; you don't have to do anything.
• compile and install egl-wayland from master (or onwards from PR #74)
• try this Firefox fix, which I didn't test. Beware that it involves manually compiling Firefox. Not recommended.

Note: in my case, because I am using a custom NVIDIA driver installer (nvidia-all), I was given the buggy 1.1.11 instead of the Arch patched version, even though I run on Arch. So I simply had to uninstall the custom egl-wayland, and instead install normally (from the extra/ repository). Quote:

Everything just works.

I already asked NOVIDEO NVIDIA about creating a new release. I hope they will do it soon.