1717715 - GLX/xwayland/Nvidia: llvmpipe is shown as active GPU#1 although WebGL tells us it's running on Nvidia

Status: NEW

(Core :: Graphics: WebRender, defect, P3)

Description

[Vash63]

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

Steps to reproduce:

1. Install xwayland-git or another branch including this patch: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/587
2. Install Nvidia 470 or higher drivers
3. Run Nightly in Xwayland (default)

Actual results:

Firefox runs fine, Compositing shows "WebRender" (no software) and WebGL shows Nvidia drivers loaded, however "GPU #1" shows the GPU as llvmpipe on mesa.

Expected results:

Firefox should run in XWayland with hardware GL acceleration.

I was able to get the exact commit that caused this with mozregression:
9:57.56 INFO: No more integration revisions, bisection finished.
9:57.56 INFO: Last good revision: 1c59701a68c9e52fcdc0bf02c02eb1dca962bc6f
9:57.56 INFO: First bad revision: c2a14298ecf313c001958c37d49cb5d9e6b7894a
9:57.56 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=1c59701a68c9e52fcdc0bf02c02eb1dca962bc6f&tochange=c2a14298ecf313c001958c37d49cb5d9e6b7894a

Comment 1

[Vash63]

Attachment: about:support information

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

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

Comment 3

[Sotaro Ikeda [:sotaro]]

This looks similar to Bug 1714069.
:rmader, can you comment to the bug?

Comment 4

[Robert Mader [:rmader]]

Vash63, once bug 1646135 has landed and a new nigthly was build (~12h from now), could you:

• provide a fresh about:support and check if the same issue is still the case
• start FF with MOZ_ENABLE_WAYLAND=1, check if things work and post the about:support
  ?

Thanks in advance!

Comment 5

[Vash63]

Attachment: new about:support

There is a change - about:support now shows a second GPU entry which is disabled, vendor ID 0x10de which is Nvidia's. This is still in XWayland.

Comment 6

[Vash63]

Attachment: about:support with Wayland native

With native Wayland the issue is totally fixed, it only shows one GPU and it is the Nvidia one. Performance is also noticeably smoother when scrolling.

Comment 7

[Vash63]

Attachment: about:support on X11 with MOZ_X11_EGL

It looks like MOZ_X11_EGL on X11 is also fixed, which broke for me over a year ago.

Comment 8

[Robert Mader [:rmader]]

Vash63: Does this still happen on more recent versions?

Comment 9

[Vash63]

(In reply to Robert Mader [:rmader] from comment #8)

Vash63: Does this still happen on more recent versions?

Yes, in XWayland it does still happen. With native Wayland the Nvidia card shows up as GPU #1.

Comment 10

[Vash63]

Attachment: Updated about:support

Oh, actually there is one change - now LLVMPIPE shows up as being used for WebGL also, the Nvidia driver isn't mentioned anywhere.

Comment 11

[Robert Mader [:rmader]]

(In reply to Vash63 from comment #10)

Oh, actually there is one change - now LLVMPIPE shows up as being used for WebGL also, the Nvidia driver isn't mentioned anywhere.

Ah, this would be a expected outcome if some library is missing from the system, egl-wayland or so. In any case, it's a setup error that Firefox does get llvmpipe as GL driver on EGL.

Comment 12

[Vash63]

(In reply to Robert Mader [:rmader] from comment #11)

(In reply to Vash63 from comment #10)

Oh, actually there is one change - now LLVMPIPE shows up as being used for WebGL also, the Nvidia driver isn't mentioned anywhere.

Ah, this would be a expected outcome if some library is missing from the system, egl-wayland or so. In any case, it's a setup error that Firefox does get llvmpipe as GL driver on EGL.

Other GL and Vulkan applications do work under XWayland for me though (and I do have egl-wayland installed, specifically this package from Nvidia's latest driver: https://trekker.guru/custom/nvidia-egl-wayland-tkg-470.63.01-175-x86_64.pkg.tar.zst )

Comment 13

[BugBot [:suhaib / :marco/ :calixte]]

The bug has a release status flag that shows some version of Firefox is affected, thus it will be considered confirmed.

Comment 14

[vortex]

Attachment: { "application": { "name": "Firefox", "osVersion": "Linux 6.5.4-1-default #1 SMP PREEMPT_DYNAMIC Wed Sep 20 05:07:04 UTC 2023 (fdd7e9e)", "version": "118.0.1", "buildID": "20230927232528", "distributionID": "mozilla-flatpak", "us

Hello there I want to add something here I found.

I run Firefox from Flathub primarily and noticed if Firefox runs via XWayland it uses llvmpipe to render causing all sorts of glitches and laggs.
However if some disables X11 using flatseal for example and let Firefox therefore run with native Wayland it uses hardware acceleration.

To verify I installed the firefox RPM package from my distribution (openSUSE Tumbleweed) inside a distrobox container and there it uses hw acceleration even if running on XWayland.

about:support flatpak - XWayland Firefox:

Comment 15

[vortex]

Hello there I want to add something here I found.

I run Firefox from Flathub primarily and noticed if Firefox runs via XWayland it uses llvmpipe to render causing all sorts of glitches and laggs.
However if some disables X11 using flatseal for example and let Firefox therefore run with native Wayland it uses hardware acceleration.

To verify I installed the firefox RPM package from my distribution (openSUSE Tumbleweed) inside a distrobox container and there it uses hw acceleration even if running on XWayland.

about:support flatpak - XWayland Firefox. Added an attachment of about:support from flatpak firefox.