Comment 58 for bug 1987976

Nice tool. It seemed like nightlies default to Wayland, so I had to test with MOZ_ENABLE_WAYLAND=0.

Bisecting the *temporary* black window gave:

 9:33.09 INFO: Last good revision: d1eb6fe5a1fa5457425c5a33f212516a5eeaa381
 9:33.09 INFO: First bad revision: 498e0e6f9b19107c8c17525a3d01a659f89002e8
 9:33.09 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=d1eb6fe5a1fa5457425c5a33f212516a5eeaa381&tochange=498e0e6f9b19107c8c17525a3d01a659f89002e8

With the mozilla-central (nightly?) builds downloaded by mozregression, I could not reproduce the main issue, the black window that remains black. Any suggestions there?

So the following was tested back on my 104.0.2 (originally downloaded from https://download.mozilla.org/?product=firefox-latest-ssl&os=linux64&lang=fr ) :

> Another interesting point would be if setting gfx.x11-egl.force-disabled (in about:config) to true helps with the issue.

No.

> Also, I suppose gfx.webrender.software:true works around the issue?

No.

Based on the bisection result, I also tried XDG_CURRENT_DESKTOP="". This changed the main issue but did not solve it. The window did not remain black, but it did not show firefox controls either.