1826937 - Firefox crashes with MOZ_ENABLE_WAYLAND=1 after upgrading to Wayland 1.22

Status: RESOLVED DUPLICATE of bug 1826583

(Core :: Graphics, defect)

Description

[henry78]

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

Steps to reproduce:

Start Firefox with MOZ_ENABLE_WAYLAND=1

I'm running Firefox 111 on Arch and Wayland with Intel and Nvidia hybrid graphics.

Actual results:

Firefox crashes:

[GFX1-]: glxtest: VA-API test failed: failed to initialise VAAPI connection.
ExceptionHandler::GenerateDump cloned child 10248
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
Exiting due to channel error.

Expected results:

Firefox starts as usual. It works fine, if I unset MOZ_ENABLE_WAYLAND (but Wayland support os not enabled in FF, so i.e. (Font) scaling is wrong).

I used MOZ_ENABLE_WAYLAND for quite some time now, it only broke after system updates, I think wayland update might be the culprit. All updates:

• coreutils (9.2-2 -> 9.2-3)
• systemd-libs (253.2-1 -> 253.2-2)
• systemd (253.2-1 -> 253.2-2)
• mesa (23.0.1-1 -> 23.0.1-2)
• lib32-mesa (23.0.1-1 -> 23.0.1-2)
• lib32-vulkan-intel (23.0.1-1 -> 23.0.1-2)
• libvirt (1:9.1.0-1 -> 1:9.2.0-1)
• libvirt-python (1:9.1.0-1 -> 1:9.2.0-1)
• openimageio (2.4.9.0-2 -> 2.4.10.0-1)
• systemd-sysvcompat (253.2-1 -> 253.2-2)
• vulkan-intel (23.0.1-1 -> 23.0.1-2)

Comment 1

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

The Bugbug bot thinks this bug should belong to the 'Core::Graphics' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[Darkspirit]

Thanks for the report! This is tracked in bug 1826583.