Blocked by: wezterm/wezterm#5263 — WezTerm must run on GNOME Wayland without the broken-pipe crash.
WezTerm crashes on GNOME Wayland with Error while flushing display: Broken pipe, so both launch paths force XWayland by clearing WAYLAND_DISPLAY:
ansible/tasks/wezterm.yml — a .desktop override with Exec=env WAYLAND_DISPLAY= wezterm start --cwd .
zsh/.config/zsh/aliases.zsh:99 — alias wezterm='WAYLAND_DISPLAY= wezterm'
Both are workarounds for wezterm/wezterm#5263, added in 86f4bd8. Removing one without the other leaves the crash reachable from the remaining path, so they come out together.
Cost of keeping it
Running under XWayland rather than native Wayland, which means blurry rendering on fractional scaling and no per-monitor DPI handling.
When wezterm#5263 is fixed
- Upgrade WezTerm, then launch it on a GNOME Wayland session both from the application grid and from a shell, with the override and alias removed.
- If stable, delete both, and drop the
desktop-only tag on tasks/wezterm.yml if nothing else remains in it.
Upstream has been open since 2024-04 and is still active, so this is not imminent. Verifying the fix needs a real GNOME Wayland session, so it cannot be confirmed by an agent or by CI.
Blocked by: wezterm/wezterm#5263 — WezTerm must run on GNOME Wayland without the broken-pipe crash.
WezTerm crashes on GNOME Wayland with
Error while flushing display: Broken pipe, so both launch paths force XWayland by clearingWAYLAND_DISPLAY:ansible/tasks/wezterm.yml— a.desktopoverride withExec=env WAYLAND_DISPLAY= wezterm start --cwd .zsh/.config/zsh/aliases.zsh:99—alias wezterm='WAYLAND_DISPLAY= wezterm'Both are workarounds for wezterm/wezterm#5263, added in 86f4bd8. Removing one without the other leaves the crash reachable from the remaining path, so they come out together.
Cost of keeping it
Running under XWayland rather than native Wayland, which means blurry rendering on fractional scaling and no per-monitor DPI handling.
When wezterm#5263 is fixed
desktop-onlytag ontasks/wezterm.ymlif nothing else remains in it.Upstream has been open since 2024-04 and is still active, so this is not imminent. Verifying the fix needs a real GNOME Wayland session, so it cannot be confirmed by an agent or by CI.