running message loop: Error while flushing display: Broken pipe (os error 32); terminating

What Operating System(s) are you seeing this problem on?

Linux Wayland

Which Wayland compositor or X11 Window manager(s) are you using?

mutter

WezTerm version

20240203-110809-5046fc22

Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?

Yes, and I updated the version box above to show the version of the nightly that I tried

Describe the bug

╰─ $ 2 wezterm -n 18:21:09.293 ERROR wezterm_gui > running message loop: Error while flushing display: Broken pipe (os error 32); terminating warning: queue 0x55601c8505f0 destroyed while proxies still attached: wl_buffer@54 still attached wl_buffer@27 still attached wl_buffer@25 still attached wl_buffer@24 still attached wl_buffer@53 still attached wl_buffer@58 still attached wl_buffer@29 still attached wl_buffer@56 still attached wl_buffer@55 still attached wl_buffer@57 still attached wl_buffer@28 still attached wl_subsurface@47 still attached wl_surface@46 still attached wl_subsurface@45 still attached wl_surface@44 still attached wl_subsurface@43 still attached wl_surface@42 still attached wl_subsurface@41 still attached wl_surface@40 still attached wl_subsurface@39 still attached wl_surface@38 still attached xdg_wm_base@21 still attached wl_surface@20 still attached wl_data_device@17 still attached wl_pointer@15 still attached zwp_text_input_v3@14 still attached wl_keyboard@13 still attached zwp_primary_selection_device_v1@12 still attached zwp_primary_selection_device_manager_v1@3 still attached wl_data_device@11 still attached zwp_text_input_manager_v3@10 still attached wl_seat@9 still attached wl_subcompositor@8 still attached wl_data_device_manager@7 still attached wl_output@6 still attached wl_shm@5 still attached wl_compositor@4 still attached

To Reproduce

This issue happen when i switch to use fractional scaling on GNOME + Wayland then reboot,

after reset use gsettings reset org.gnome.mutter experimental-features, but it still not work.

Configuration

No config.

Expected Behavior

No response

Logs

No response

Anything else?

No response