Bug 1768358 Comment 12 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
Please open about:support, click on "Copy text to clipboard" and paste it [here](https://bugzilla.mozilla.org/attachment.cgi?bugid=1768358&action=enter) so that we are 100% sure about whether you use Wayland or Xwayland.

> AdapterDriverVersion: 470.103.1.0

Having driver 470 (=minimum required version for hardware rendering: bug 1742994) might be the reason alone
because it doesn't fully support Wayland.
Please upgrade to Nvidia driver 495 or >= 510.  

* 470 introduced support for Dmabuf (but not Gbm yet), had some Xwayland EglStreams improvement. (https://www.phoronix.com/scan.php?page=news_item&px=NVIDIA-470-Wayland-Friendly, https://www.phoronix.com/scan.php?page=news_item&px=XWayland-Load-Correct-NV-GLX)
  * Instead of trying WR/EGLStreams Xwayland, Wayland users with driver 470 should rather get 
    * MOZ_ENABLE_WAYLAND by default (wayland is not officially shipped yet: bug 1752398)
    * or SW WR/EGLStreams Xwayland: **It might be good to add a blocklist entry** that requires 495 for hardware WebRender/Nvidia/**Xwayland**.
* The first version that actually supported Gbm (and not only Nvidia's EGLStreams) for Wayland was 495 (https://www.phoronix.com/scan.php?page=news_item&px=NVIDIA-495.44-Linux-Driver).
* Driver >= 510 is recommended for Wayland.

Ubuntu switched its Firefox build from Wayland to back to xwayland because Mozillas hasn't officially shipped Wayland yet.
Xwayland/Nvidia can be broken of multiple reasons (nvidia driver version, egl-wayland version, xwayland version, multiple graphics cards, etc, bug 1717715, bug 1736245). X11/Nvidia has worse performance than Wayland/Nvidia (bug 1736245).
IIUC, Native Wayland should always be prefferred on Nvidia.

In case this problem also occurs with 495 or >= 510, please check if starting Firefox with MOZ_ENABLE_WAYLAND=1 environment variable avoids the problem:
`$ MOZ_ENABLE_WAYLAND=1 snap run firefox` (bug 1767231 has been fixed)
`$ MOZ_ENABLE_WAYLAND=1 path/to/firefox`
Revision 1 by
on 
Please open about:support, click on "Copy text to clipboard" and paste it [here](https://bugzilla.mozilla.org/attachment.cgi?bugid=1768358&action=enter) so that we are 100% sure about whether you use Wayland or Xwayland.

> AdapterDriverVersion: 470.103.1.0

Having driver 470 (=minimum required version for hardware rendering: bug 1742994) might be the reason alone
because it doesn't fully support Wayland.
Please upgrade to Nvidia driver 495 or >= 510.  

* 470 introduced support for Dmabuf (but not Gbm yet), had some Xwayland EglStreams improvement. (https://www.phoronix.com/scan.php?page=news_item&px=NVIDIA-470-Wayland-Friendly, https://www.phoronix.com/scan.php?page=news_item&px=XWayland-Load-Correct-NV-GLX)
  * Instead of trying WR/EGLStreams Xwayland, Wayland users with driver 470 should rather get 
    * MOZ_ENABLE_WAYLAND by default (wayland is not officially shipped yet: bug 1752398)
    * or SW WR/EGLStreams Xwayland: **It might be good to add a blocklist entry** that requires 495 for hardware WebRender/Nvidia/**Xwayland**.
* The first version that actually supported Gbm (and not only Nvidia's EGLStreams) for Wayland was 495 (https://www.phoronix.com/scan.php?page=news_item&px=NVIDIA-495.44-Linux-Driver).
* Driver >= 510 is recommended for Wayland.

Ubuntu switched its Firefox build from Wayland to back to xwayland because Mozillas hasn't officially shipped Wayland yet.
Xwayland/Nvidia can be broken of multiple reasons (nvidia driver version, egl-wayland version, xwayland version, multiple graphics cards, etc, bug 1717715). X11/Nvidia has worse performance than Wayland/Nvidia (bug 1736245).
IIUC, Native Wayland should always be prefferred on Nvidia.

In case this problem also occurs with 495 or >= 510, please check if starting Firefox with MOZ_ENABLE_WAYLAND=1 environment variable avoids the problem:
`$ MOZ_ENABLE_WAYLAND=1 snap run firefox` (bug 1767231 has been fixed)
`$ MOZ_ENABLE_WAYLAND=1 path/to/firefox`
Revision 2 by
on 
Please open about:support, click on "Copy text to clipboard" and paste it [here](https://bugzilla.mozilla.org/attachment.cgi?bugid=1768358&action=enter) so that we are 100% sure about whether you use Wayland or Xwayland.

> AdapterDriverVersion: 470.103.1.0

Having driver 470 (=minimum required version for hardware rendering: bug 1742994) might be the reason alone
because it doesn't fully support Wayland.
Please upgrade to Nvidia driver 495 or >= 510.  

* 470 introduced support for Dmabuf (but not Gbm yet), had some Xwayland EglStreams improvement. (https://www.phoronix.com/scan.php?page=news_item&px=NVIDIA-470-Wayland-Friendly, https://www.phoronix.com/scan.php?page=news_item&px=XWayland-Load-Correct-NV-GLX)
  * Instead of trying WR/EGLStreams Xwayland, Wayland users with driver 470 should rather get 
    * MOZ_ENABLE_WAYLAND by default (wayland is not officially shipped yet: bug 1752398)
    * or SW WR/EGLStreams Xwayland: **It might be good to add a blocklist entry** that requires 495 for hardware WebRender/Nvidia/**Xwayland**.
* The first version that actually supported Gbm (and not only Nvidia's EGLStreams) for Wayland was 495 (https://www.phoronix.com/scan.php?page=news_item&px=NVIDIA-495.44-Linux-Driver).
* Driver >= 510 is recommended for Wayland.

Ubuntu switched its Firefox build from Wayland to back to xwayland because Mozillas hasn't officially shipped Wayland yet.
Xwayland/Nvidia can be broken of multiple reasons (nvidia driver version, egl-wayland version, xwayland version, multiple graphics cards, etc, bug 1717715). X11/Nvidia has worse performance than Wayland/Nvidia (bug 1736245).
IIUC, Native Wayland should always be preferred on Nvidia.

In case this problem also occurs with 495 or >= 510, please check if starting Firefox with MOZ_ENABLE_WAYLAND=1 environment variable avoids the problem:
`$ MOZ_ENABLE_WAYLAND=1 snap run firefox` (bug 1767231 has been fixed)
`$ MOZ_ENABLE_WAYLAND=1 path/to/firefox`

Back to Bug 1768358 Comment 12