Closed Bug 1670492 Opened 4 years ago Closed 4 years ago

Firefox is rendering a black page

Categories

(Core :: Graphics, defect)

Firefox 81
defect

Tracking

()

RESOLVED DUPLICATE of bug 1646135

People

(Reporter: thezombiehunter, Unassigned)

Details

Attachments

(1 file)

Attached image firefox.jpeg

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

Steps to reproduce:

Started firefox.

Currently using:
Linux/Gentoo with ~amd64 testing branch, using firefox-bin package.
KDE with Wayland / EGLStreams
Nvidia GPU
1440p display + 4k display

Actual results:

Black page

Expected results:

Firefox starts correctly

Component: Untriaged → Graphics
Product: Firefox → Core

Thanks for the report!
For the moment, please use Wayland with Mesa, or X11, if you want to use hardware rendering. The other option is using software rendering.
gfx.webrender.all is the new OpenGL renderer, layers.acceleration.force-enabled is the old one. It seems you have enabled one of them.

Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE

(In reply to Darkspirit from comment #1)

Thanks for the report!
For the moment, please use Wayland with Mesa, or X11, if you want to use hardware rendering. The other option is using software rendering.
gfx.webrender.all is the new OpenGL renderer, layers.acceleration.force-enabled is the old one. It seems you have enabled one of them.

*** This bug has been marked as a duplicate of bug 1646135 ***

The problem with software rendering (which does work) is that on my 4k monitor the browser becomes unusable due to low fps/lag.

Works decently on my QHD monitor though.

I just want to know if this issue is getting looked into or if firefox will not support the proprietary nvidia driver. No rush here.

Flags: needinfo?(jan)

As a volunteer, I really don't know, but it seems unlikely other contributors would look at it soon. Getting hardware rendering finally shipped to X11/Mesa, Wayland/Mesa and perhaps X11/proprietary Nvidia are the main focus. It would be great though if new contributors could look at it!
Nvidia's non-standard hack (EGLStreams) to support Wayland isn't enabled in Ubuntu yet and only two Wayland compositors support it at all.
It would be helpful if Nvidia supported Wayland properly through established standards (GBM, Dmabuf), especially by providing the required signed firmware for reclocking and video decoding to Mesa/Nouveau.

Flags: needinfo?(jan)

(In reply to Darkspirit from comment #3)

Nvidia's non-standard hack (EGLStreams) to support Wayland isn't enabled in Ubuntu yet and only two Wayland compositors support it at all.

I think everyone can agree that nvidia supporting GBM would be the right move.

Unfortunately they will not support GBM and 75% or so of the market uses nvidia according to the steam survey.

If wayland is to move forward and replace X11 EGLStreams is going to have to be supported by the majority of software.

And while my next card is going to be AMD that doesn't change that my card is currently nvidia. Since i have a 2080 it's going to be some time before I purchase another GPU.

(In reply to SimplyCorbett from comment #4)

Unfortunately they will not support GBM and 75% or so of the market uses nvidia according to the steam survey.

The situation is not that bad. Steam Linux numbers from 2020-09-30:
54.05% have excellent Mesa support (AMD/Intel),
45.95% have throttled Mesa performance (Nvidia). Nvidia is partially already working on improving Mesa/Nouveau.

If wayland is to move forward and replace X11 EGLStreams is going to have to be supported by the majority of software.

Sure. (IIRC, no large distro has announced plans yet whether they enable Nvidia's non-standard Wayland support by default.)

Well, fingers crossed. :)

Yeah AMD is gaining a good foothold. I'll be swapping when given the chance but their current cards compete with the 2080 so there is no reason to swap. I'll see what big navi has in store with RDNA 2!

Thank you for taking the time to reply and let me know what's up with things.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: