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

[munzirtaha]

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

Linux Wayland

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

kwin

WezTerm version

20230712-072601-f4abf8fd

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

No, and I'll explain why below

Describe the bug

When I run hb-view command over a font folder in wezterm, my system freezes. I cannot move my mouse or do anything while the command is running. Sometimes, wezterm crash with the error in the title. The full journalctl entry is

Dec 25 23:02:57 lenovo kwin_wayland_wrapper[248885]: 23:02:57.871 ERROR wezterm_gui > running message loop: Error while flushing display: Broken pipe (os error 32); terminating

I tried the same command in konsole and there is no issue at all.

To Reproduce

cd ~/.local/share/fonts/Windows/
for i in *; hb-view $i "The quick brown fox jumps over the lazy dog"; end

Configuration

no config

Expected Behavior

No performance lag or crash

Logs

00:15:44.533 DEBUG wezterm_gui::termwindow > Notification(Any { .. })
00:15:44.533 DEBUG wezterm_gui::termwindow > Notification(Any { .. })
00:15:44.533 DEBUG wezterm_gui::termwindow > Notification(Any { .. })

Anything else?

No response

[jfftck]

I, too, have this issue on Ubuntu 24.04 in Wayland, here is the error:

 ERROR  wezterm_gui > running message loop: Error while flushing display: Broken pipe (os error 32); terminating
warning: queue 0x59a23d87ce40 destroyed while proxies still attached:
  wl_buffer@64 still attached
  wl_buffer@63 still attached
  wl_buffer@62 still attached
  wl_buffer@61 still attached
  wl_buffer@60 still attached
  wl_buffer@59 still attached
  wl_buffer@58 still attached
  wl_buffer@57 still attached
  wl_buffer@56 still attached
  wl_buffer@30 still attached
  wl_buffer@29 still attached
  wl_subsurface@48 still attached
  wl_surface@47 still attached
  wl_subsurface@46 still attached
  wl_surface@45 still attached
  wl_subsurface@44 still attached
  wl_surface@43 still attached
  wl_subsurface@42 still attached
  wl_surface@41 still attached
  wl_subsurface@40 still attached
  wl_surface@39 still attached
  xdg_wm_base@22 still attached
  wl_surface@21 still attached
  wl_data_device@18 still attached
  wl_pointer@16 still attached
  zwp_text_input_v3@15 still attached
  wl_keyboard@14 still attached
  zwp_primary_selection_device_v1@13 still attached
  zwp_primary_selection_device_manager_v1@3 still attached
  wl_data_device@12 still attached
  zwp_text_input_manager_v3@11 still attached
  wl_seat@10 still attached
  wl_subcompositor@9 still attached
  wl_data_device_manager@8 still attached
  wl_output@7 still attached
  wl_output@6 still attached
  wl_shm@5 still attached
  wl_compositor@4 still attached
  wl_registry@2 still attached

I tried both the AppImage and native install, so it has to do with Wayland support not ready for this terminal -- which is a shame, as I was looking forward to trying this one.

[ghost]

Updated Manjaro with Gnome
wezterm 20240203-110809-5046fc22
Works fine with 100% and 200% scale.
Crashes with error on fractional scales:

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

[MichaelBrunn3r]

Gnome 46 Wayland
NixOS 24.05
wezterm 20240203-110809-5046fc22

Experimental mutter feature scale-monitor-framebuffer enabled.

Same behaviour as @makoven. 100% & 200% work without issue, settings it to 125% it suddendly crashes

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

Edit: Might be a Gnome only problem. Switching to KDE fixed the issue. "experimental" is in the name.

[wez]

Please try running the latest nightly build

[munzirtaha]

I confirm it's now fixed. Thanks a lot Mr. wez. However, when I use SHIFT-PageUp and SHIFT-PageDown to scroll the viewport, it's very slow compared with Konsole

[github-actions]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

[munzirtaha]

I already responded and confirmed the error is no longer there but there is an issue with performance. If this should be a separate issue or the performance lag is expected for some reason, I will accept closing the bug but just to let you know

[robey]

Just upgraded to ubuntu 24.04 and seeing this, so it's still happening.

Also, the nightly build tries to extend beyond the screen limits and crashes after a few seconds of trying to adjust it. It seems to take down gnome with it. 🤣

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.