Steps to reproduce:

Upgrade from Firefox 113 to Firefox 114.

  "application": {
    "name": "Firefox",
    "osVersion": "Linux 6.3.5-200.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Tue May 30 15:44:17 UTC 2023",
    "version": "114.0",
    "buildID": "20230606090644",
    "distributionID": "fedora",
    "userAgent": "Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/114.0",
    "safeMode": false,
    "memorySizeBytes": 32704274432,
    "diskAvailableBytes": 713725194240,
    "supportURL": "https://support.mozilla.org/1/firefox/114.0/Linux/en-US/",
    "osTheme": "Breeze / Adwaita",
    "numTotalWindows": 2,
    "numFissionWindows": 2,
    "numRemoteWindows": 2,
    "fissionAutoStart": true,
    "fissionDecisionStatus": "enabledByDefault",
    "remoteAutoStart": true,
    "policiesStatus": 0,
    "keyLocationServiceGoogleFound": true,
    "keySafebrowsingGoogleFound": true,
    "keyMozillaFound": true
  },

Actual results:

Hardware acceleration does not work.

about:support reports

    "failures": [
      "[GFX1-]: glxtest: ManageChildProcess failed\n",
      "[GFX1-]: glxtest: X error, error_code=10, request_code=152, minor_code=5"
    ],

(full log attached)

Expected results:

Hardware acceleration should work.

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.

Thanks for the report!
Please

• post the output of: $ MOZ_GFX_DEBUG=1 firefox
• attach the output of $ glxinfo > glxinfo.txt 2>&1 and of $ vainfo > vainfo.txt 2>&1

My system doesn't seem to have vainfo. glxinfo.txt is attached.

$ MOZ_GFX_DEBUG=1 firefox
GLX_TEST: childgltest start
GLX_TEST: get_pci_status start
GLX_TEST: get_pci_status finished
GLX_TEST: x11_egltest start
GLX_TEST: get_egl_status start
GLX_TEST: get_egl_gl_status start
GLX_TEST: get_egl_gl_status finished
GLX_TEST: get_egl_status finished with return: 1
GLX_TEST: glxtest start
PCI_VENDOR_ID
0x1002
PCI_DEVICE_ID
0x164e
PCI_VENDOR_ID
0x1002
PCI_DEVICE_ID
0x73bf
DRI_DRIVER
radeonsi
VENDOR
AMD
RENDERER
AMD Radeon RX 6800 XT (navi21, LLVM 16.0.4, DRM 3.52, 6.3.5-200.fc38.x86_64)
VERSION
4.6 (Compatibility Profile) Mesa 23.1.1
TFP
TRUE
DRM_RENDERDEVICE
/dev/dri/renderD128
MESA_VENDOR_ID
0x1002
MESA_DEVICE_ID
0x73bf
ERROR
X error, error_code=10, request_code=152, minor_code=5
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: ManageChildProcess failed
 (t=0.327917) [GFX1-]: glxtest: ManageChildProcess failed

Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: ManageChildProcess failed
 (t=0.327917) |[1][GFX1-]: glxtest: X error, error_code=10, request_code=152, minor_code=5 (t=0.327934) [GFX1-]: glxtest: X error, error_code=10, request_code=152, minor_code=5

Thanks! Please also attach the output of: $ eglinfo > eglinfo.txt 2>&

(In reply to David Warner from comment #4)

My system doesn't seem to have vainfo.

David, you can get vainfo by installing the libva-utils package on Fedora. Similarly, eglinfo is in egl-utils package. (You can figure this out next time by running sudo dnf provides /usr/bin/vainfo command or similar).

^ Added the eglinfo output. I notice it's a bit different when I run it as a regular user (eglinfo-su.txt is the output of sudo eglinfo).

(In reply to Kamil Páral from comment #6)

(In reply to David Warner from comment #4)

My system doesn't seem to have vainfo.

David, you can get vainfo by installing the libva-utils package on Fedora. Similarly, eglinfo is in egl-utils package. (You can figure this out next time by running sudo dnf provides /usr/bin/vainfo command or similar).

Thanks - here's the output:

libva info: VA-API version 1.18.0
libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_18
libva info: va_openDriver() returns 0
Trying display: wayland
Trying display: x11
vainfo: VA-API version: 1.18 (libva 2.18.2)
vainfo: Driver version: Mesa Gallium driver 23.1.1 for AMD Radeon RX 6800 XT (navi21, LLVM 16.0.4, DRM 3.52, 6.3.5-200.fc38.x86_64)
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            : VAEntrypointVLD
      VAProfileMPEG2Main              : VAEntrypointVLD
      VAProfileVC1Simple              : VAEntrypointVLD
      VAProfileVC1Main                : VAEntrypointVLD
      VAProfileVC1Advanced            : VAEntrypointVLD
      VAProfileH264ConstrainedBaseline: VAEntrypointVLD
      VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
      VAProfileH264Main               : VAEntrypointVLD
      VAProfileH264Main               : VAEntrypointEncSlice
      VAProfileH264High               : VAEntrypointVLD
      VAProfileH264High               : VAEntrypointEncSlice
      VAProfileHEVCMain               : VAEntrypointVLD
      VAProfileHEVCMain               : VAEntrypointEncSlice
      VAProfileHEVCMain10             : VAEntrypointVLD
      VAProfileHEVCMain10             : VAEntrypointEncSlice
      VAProfileJPEGBaseline           : VAEntrypointVLD
      VAProfileVP9Profile0            : VAEntrypointVLD
      VAProfileVP9Profile2            : VAEntrypointVLD
      VAProfileAV1Profile0            : VAEntrypointVLD
      VAProfileNone                   : VAEntrypointVideoProc

Please try to run '/usr/lib64/firefox/glxtest' directly. Do you get the same result, i.e. X error ?

eglinfo

X11 platform:

0x01 32 0 10 10 10 2 0 0 0 0 0x21TC a y y y win,pb,pix
0x02 32 0 10 10 10 2 16 0 0 0 0x21TC a y y y win,pb,pix
0x03 32 0 10 10 10 2 24 0 0 0 0x21TC a y y y win,pb,pix
0x04 32 0 10 10 10 2 24 8 0 0 0x21TC a y y y win,pb,pix

glxinfo

504 GLX Visuals

0x021 30 tc 0 32 0 r y . 10 10 10 2 . . 0 24 8 0 0 0 0 0 0 u None

glxtest

GLX_TEST: get_egl_status finished with return: 1
GLX_TEST: glxtest start

egltest is aborted because you have likely added (so far) unsupported DefaultDepth 30 to your xorg.conf,
glxtest is then tried and fails with

X error, error_code=10, request_code=152, minor_code=5

which seems to be glXMakeCurrent: https://searchfox.org/mozilla-central/rev/887d4b5da89a11920ed0fd96b7b7f066927a67db/toolkit/xre/glxtest/glxtest.cpp#789

This unrelated project has the same error: https://github.com/alacritty/alacritty/issues/6005#issuecomment-1101410310

thread 'main' panicked at 'glXMakeCurrent failed: Err(XError { description: "BadAccess (attempt to access private resource denied)", error_code: 10, request_code: 152, minor_code: 5 })', /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/glutin-0.28.0/src/api/glx/make_current_guard.rs:78:13

(In reply to Darkspirit from comment #12)

egltest is aborted because you have likely added (so far) unsupported DefaultDepth 30 to your xorg.conf,

Thanks, that's exactly it.

Firefox 113 and earlier versions seemed to be generally running fine with the unsupported DefaultDepth 30 - is there any way to have Firefox ignore the glxtest result?

(In reply to Martin Stránský [:stransky] (ni? me) from comment #11)

Please try to run '/usr/lib64/firefox/glxtest' directly. Do you get the same result, i.e. X error ?

Yes, I get the same error that MOZ_GFX_DEBUG=1 firefox reports.

Please attach about:support of Firefox 113.

Thanks Darkspirit. I think we should handle it better. But I wonder why it worked before.

Sorry, Fedora isn't making it easy to go back to 113 - in the meantime I've attached about:support from Firefox 111.

Please attach about:support of Firefox 114 started with this command:
$ MOZ_WEBRENDER=1 MOZ_X11_EGL=1 firefox

$ MOZ_WEBRENDER=1 MOZ_X11_EGL=1 firefox
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: ManageChildProcess failed
 (t=0.216274) [GFX1-]: glxtest: ManageChildProcess failed

Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: ManageChildProcess failed
 (t=0.216274) |[1][GFX1-]: glxtest: X error, error_code=10, request_code=152, minor_code=5 (t=0.216296) [GFX1-]: glxtest: X error, error_code=10, request_code=152, minor_code=5

about:support from MOZ_WEBRENDER=1 MOZ_X11_EGL=1 firefox

Please start Firefox 114, set webgl.force-enabled to true on about:config, close Firefox 114.
Start Firefox 114 with $ MOZ_WEBRENDER=1 MOZ_X11_EGL=1 firefox
and attach its about:support.

(In reply to David Warner from comment #17)

Sorry, Fedora isn't making it easy to go back to 113 - in the meantime I've attached about:support from Firefox 111.

You can download rpm from https://koji.fedoraproject.org/koji/buildinfo?buildID=2205210
(you need firefox and firefox-langpacks for x86_64) and then run as root

rpm -Uhv --oldpackage firefox*rpm  firefox-langpacks*rpm

(with webgl.force-enabled set to true)

$ MOZ_WEBRENDER=1 MOZ_X11_EGL=1 firefox
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: ManageChildProcess failed
(t=0.170396) [GFX1-]: glxtest: ManageChildProcess failed

Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: ManageChildProcess failed
(t=0.170396) |[1][GFX1-]: glxtest: X error, error_code=10, request_code=152, minor_code=5 (t=0.170414) [GFX1-]: glxtest: X error, error_code=10, request_code=152, minor_code=5

(In reply to Martin Stránský [:stransky] (ni? me) from comment #22)

(In reply to David Warner from comment #17)

Sorry, Fedora isn't making it easy to go back to 113 - in the meantime I've attached about:support from Firefox 111.

You can download rpm from https://koji.fedoraproject.org/koji/buildinfo?buildID=2205210
(you need firefox and firefox-langpacks for x86_64) and then run as root

rpm -Uhv --oldpackage firefox*rpm  firefox-langpacks*rpm

Thanks - I've re-installed 113 and attached about:support.

(In reply to David Warner from comment #13)

Firefox 113 and earlier versions seemed to be generally running fine with the unsupported DefaultDepth 30 - is there any way to have Firefox ignore the glxtest result?

No, as long as you keep DefaultDepth 30, Mesa won't offer an RGBA8888 EGL config on X11 which means no EGL hardware rendering, no EGL-Dmabuf DRM-VAAPI hardware video decoding and no fast EGL-Dmabuf WebGL.

Try starting Firefox with MOZ_ENABLE_WAYLAND=1 environment variable on KDE Wayland.

Firefox 114 seems fine in the KDE Wayland session.

Performance with MOZ_WEBRENDER=1 MOZ_X11_EGL=1 firefox (under X) seems fine - playing a video doesn't cause CPU usage to go crazy. Is this practically what I was getting with Firefox 113 (still no EGL rendering)?

https://hg.mozilla.org/mozilla-central/rev/76e29d4bec7b