Hardware acceleration on Firefox

where it states that Window Protocol should be “wayland/drm” instead of just “wayland”.

I don’t know why it says wayland instead of wayland/drm. I’ve run across this multiple times and can’t seem to tell what difference it makes, or why.

BTW: VA-API seems to just work with firefox-wayland if you enable WR and VAAPI (gfx.webrender.enabled) and (widget.wayland-dmabuf-vaapi.enabled).

Also, I rebased and would like us to reconsidering merging this: firefox-wrapper: rename gdkWayland->forceWayland; always use libglvnd by colemickens · Pull Request #73365 · NixOS/nixpkgs · GitHub and make libglvnd available to firefox by default. In my opinion, we should encourage people to set MOZ_ENABLE_WAYLAND=1 and use firefox and keep firefox-wayland as legacy until MOZ_ENABLE_WAYLAND is deprecated in favor of an inverted flag.

It also has the benefit of making using firefox the same as using the other firefox derivations that respect the same convention. firefox-wayland is the odd-ball now.

I kind of wonder if others were using firefox like me and couldn’t get vaapi working because WR wasn’t actually working right…

3 Likes