1839130 - [Flatpak] Nvidia+AMD dual GPU: WebGL not working on flatpaked firefox

Status: UNCONFIRMED

(Firefox Build System :: Third Party Packaging, defect, P3)

Description

[jjcasmar]

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

Steps to reproduce:

I have a system with two GPUs, a nVidia one and a AMD one. In that system, I can run firefox normally with WebGL. However, if instead of using the "native" version of firefox, I use the flatpaked one, WebGL doesn't work.

Actual results:

When I run flatpak run org.mozilla.firefox, I get the following error

flatpak run org.mozilla.firefox                                                                            
[GFX1-]: glxtest: libEGL no display
[GFX1-]: glxtest: EGL test failed
[GFX1-]: More than 1 GPU vendor detected via PCI, cannot deduce vendor

[GFX1-]: PCI candidate 0x10de/0x1e84

[GFX1-]: PCI candidate 0x1002/0x743f

I have read several bug reports that says that the error itself is not a real issue and its harmless. However, I have no WebGL.

Expected results:

WebGL should work

Comment 1

[jjcasmar]

Attachment: about:support report

about:support reports the following

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 correct in case you think the bot is wrong.

Comment 3

[Darkspirit]

https://searchfox.org/mozilla-release/rev/2be4fd198990dc742793fd1ba611888fb640e7f7/widget/gtk/GfxInfo.cpp#476

Comment 4

[Glenn Watson [:gw]]

Kelsey, any ideas who would be the right person to ask about this?

Comment 5

[jjcasmar]

Any update on this?

Comment 6

[Marco Castelluccio [:marco]]

Given that this only happens with Flatpak, let's reduce severity to S3.

Comment 7

[Kelsey Gilbert [:jgilbert]]

I think Flatpak issues are generally related to sandboxing, but whether our fault or theirs is TBD.

Comment 8

[Gian-Carlo Pascutto [:gcp]]

Martin, is this something you can help with?

Comment 9

[Jed Davis [:jld] ⟨⏰|UTC-7⟩ ⟦he/him⟧]

(In reply to Kelsey Gilbert [:jgilbert] from comment #7)

I think Flatpak issues are generally related to sandboxing, but whether our fault or theirs is TBD.

In this case it's affecting glxtest, so it's not our sandbox.

It may help that glxtest is a separate executable now, so it's possible to do flatpak run --command=/app/lib/firefox/glxtest org.mozilla.firefox to run it in the Flatpak sandbox. This would need a little more work to run it under a debugging tool like strace or gdbserver, but there might be less invasive ways of troubleshooting this, like Mesa's environment variables (I'm not a graphics expert so I don't know exactly which ones might help).

Comment 10

[Martin Stránský [:stransky] (ni? me)]

Reporter, first of all please test latest version and then run Firefox/flatpak from terminal as:

flatpak run --env=MOZ_GFX_DEBUG=1 org.mozilla.firefox

and attach the output here.
Thanks.

Comment 11

[jjcasmar]

Hi,

apparently the issue has nothing to do with firefox. Its an issue in flatpak. Since I have 2 GPUs, I have defined several environment variables on the host system, __GLX_VENDOR_LIBRARY_NAME, __EGL_VENDOR_LIBRARY_FILENAMES and VK_ICD_FILENAMES. Flatpak picks this variables for the container, and inside the container the libraries are in other locations, so it doesn't find them.

https://github.com/flatpak/flatpak/issues/5543

Comment 12

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

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

For more information, please visit BugBot documentation.