The issue has been closed and supposedly fixed. The target milestone has been set to 125, which I assume means that it should be included in the Firefox 125 release planned for 16 April 2024. In the meantime, the recommended workaround is to run Firefox with `MOZ_DISABLE_WAYLAND_PROXY=1`.
The Firefox issue can be found at: https:/ /bugzilla. mozilla. org/show_ bug.cgi? id=1882449
The issue has been closed and supposedly fixed. The target milestone has been set to 125, which I assume means that it should be included in the Firefox 125 release planned for 16 April 2024. In the meantime, the recommended workaround is to run Firefox with `MOZ_DISABLE_ WAYLAND_ PROXY=1` .