Next Release Checklist

[wez]

BEFORE YOU COMMENT: please avoid duplicating information from other comments to avoid overwhelming this one.
Prefer to use a thumbs up instead of a me-too comment.

We're overdue for making a new release.
Here's what's on my mind as release gating issues, and I need your help to check these off.
So if you are interested in having a new stable tag, please help by running through the list below and giving some feedback on the state of these things for your system:

• Verify that Wayland support isn't an obvious regression since the last stable release.

  • Wayland support was essentially rewritten by the community, and since I don't use wayland, I don't have sufficient context now to understand where it has problems either in the code or due to compatibility.
  • If you are a Wayland user, and you are using a wezterm nightly build from October 2024 or later and having a good experience, please comment below with the name of your compositor and DE to say that it is as good as or better than the prior stable release.
  • If there is already a comment describing your environment, instead of posting a duplicate, please give it a thumbs-up reaction to "vote" for it if it is working well for you.
  • If it isn't working working as well or better than the prior stable release, please reference an issue that describes the problem and comment below.

• Verify that the default configuration doesn't crash out.

  • Run wezterm -n on your system to launch it without your config. Does it successfully launch and display text with no artifacts or blocks for glyphs?
  • If not:
    • try changing the front_end setting to see if that is better:
    • wezterm -n --config "front_end='WebGpu'"
    • Please find/file an issue reporting the outcome of both the default and webgpu, along with information about the environment. If the behavior is a regression since the prior stable release, reference that issue here.

• Confirm that we're building for the current batch of OS/distros

  • Add CI for Fedora Linux 41, drop Fedora Linux 38 as it's EOL #6156
  • Alter copr spec file for Fedora 41 and Rawhide #6200
  • Others? Please comment here

• Other misc issues:

  • Fix alternate-screen scrolling #6186

[rootiest]

KDE Plasma 6 (Wayland) working great for me on nightly.

[jankatins]

I'm on Gnome 46/Mutter with Windowing system Wayland (fedora 40 workstation, up to date until yesterday), using wezterm 20241027_002434_14ad1937.

Stuff which I "notice" (I seem to remember that it worked sometime before the rewrite or when I was still on macosx). This is all with config.enable_wayland = true or not having that config set at all:

• I don't have an additional title bar (which is fine-ish) and double click on the tab bar to maximize does not work (which is bad). I added that as a config in Gnome: Allow double click on title bar to maximize the window when using Wayland CSD #2831
• I don't have min/max/close buttons in the tab bar, which I kind of think where there earlier? As there is also no title bar, I need to use 'win+up' to toogle maximize (which I configured in gnome)
• I cannot move the window anymore: Title Bar is missing under Mutter #6296
• I use a gui-startup event handler to window:gui_window():maximize() -> my window still comes up unmaximized -> Prob Maximize is not working and fullscreen is not fullscreen #6203
• If I configure config.window_decorations = "INTEGRATED_BUTTONS", I get an additional (black and completely different form the rest of the windows on gnome) title bar with the min/max/close buttons and max and close work. I can also move the window around when I start dragging on that new title bar. Still, double click on that title bar to maximize does NOT work and the min button also does NOT work: Using INTEGRATED_BUTTONS decorations on Linux, the minimize button is nonfunctional #6086 (this might be a general error, as the issue was reported on x11)
• With config.window_decorations = "INTEGRATED_BUTTONS" The full screen window "overflows" at the bottom. maximized window overflows bottom of screen when using Wayland CSD #6318

If I run with config.enable_wayland = false, I have a (grey, like the rest of GNOME) additional title bar with a single close button, I can move the window around, even when I was in fullscreen, it starts in full screen, and the window overflow problem is also gone.

So all in all: Using config.window_decorations = "INTEGRATED_BUTTONS" and some additional config.window_padding = {...} I can live with using wezterm (with config.enable_wayland = true) as my daily driver, but I'm also currently embarrassed to show my terminal window to colleagues who use warp or alacritty or recommend it to ppl. who would usually benefit from a cross platform terminal :-(

Relevant Gnome config:

gsettings set org.gnome.desktop.wm.keybindings maximize "['<Super>Up']"
gsettings set org.gnome.desktop.wm.preferences action-double-click-titlebar 'toggle-maximize'

[UnaTried]

wezterm-git (20241030.215404.f847bd28-1)
on
Hyprland (v0.44.0-73-g3cec45d8)
on
Arch Linux (Kernerls: linux [6.11.5-arch1-1], linux-lts [6.6.58-1] and linux-zen [6.11.5.zen1-1])

Output from running "wezterm" on kitty and having wayland support off:

22:58:46.242  ERROR  wezterm_client::client > IncompatibleVersionError { version: "20240203-110809-5046fc22", codec_vers: 42 }
22:58:46.259  WARN   window::os::wayland::connection > Unable to resolve appearance using xdg-desktop-portal: get_appearance.read_setting: Reading xdg-portal org.freedesktop.appearance color-scheme: org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.freedesktop.portal.Settings” on object at path /org/freedesktop/portal/desktop

With wayland support on:

23:08:08.738  WARN   window::os::wayland::connection > Unable to resolve appearance using xdg-desktop-portal: get_appearance.read_setting: Reading xdg-portal org.freedesktop.appearance color-scheme: org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.freedesktop.portal.Settings” on object at path /org/freedesktop/portal/desktop

[nekowinston]

There's a regression on Sway 1.10.
Nightly works for me on Sway 1.9, but I'm guessing the new wlroots-0.18 in 1.10 broke parts of the WezTerm Wayland implementation.

	WezTerm stable	WezTerm nightly (f847bd28)
Sway 1.9	❌ Logs	✅ Logs
Sway 1.10	❌ Logs	❌ Logs

Tested on NixOS unstable, Linux 6.11.5, x86_64-linux.

All logs are collected via:

WAYLAND_DEBUG=1 WEZTERM_LOG=window::os::wayland=trace cargo r --release --bin wezterm-gui -- -n --config "front_end='WebGpu'"

It's worth mentioning that [email protected] initially renders blurry text, which goes away after scaling/moving/maximizing the window once. But overall, I had a pretty reliable experience on Wayland on Sway 1.9.

---

As for Sway 1.10:

I've tried to chase down the error with a debug build & debugging via CodeLLDB, all I could gather from it, is that it crashes around here.
It seems to crash after a few iterations, so it makes debugging a bit frustrating; I'm happy to dive back in tho.
Sometimes it also doesn't crash, but "hangs", in that it logs loading the config, and rendering the cursor block etc, but simply won't render the terminal window. I'd say that happens on about 1/4th(?) of the launches.

[dani162]

wezterm 20241031_235112_0983ae90
Fedora 41 - Gnome 47 - Wayland

• I would say the current nightly is much more stable than the current release (the current release wont even start anymore on my system). I am having the following issue with the current release, seems to be fixed in nightly. Weird issue when using wezterm on gnome wayland #6191
  I remember switching to the nightly version, because the release version kept on crashing all the time (Probably this was also related to fractional scaling)

Probably Regressions:

• WezTerm behaves a bit buggy with fractional scaling enabled. When I open WezTerm on my Primary Monitor (150% Scaling, 3840x2160 Resolution) Wezterm has no icon in the dock where the open apps are displayed and is shown as Unknown Application. If i open WezTerm on my secondary Monitor (100% Scaling, 1920x1080 Resolution) it works fine.
  
  Screenshot of Gnome Looking Glass Debug Tool (Alt + F2 - type lg). The First Application is WezTerm on the Monitor without Fractional Scaling, Second with Fractional Scaling (150%). I noticed that when opening the app, the icon is correct for a short time, but WezTerm immediately closes and reopens, only that the icon no longer works. This, closing and reopening behavior also happens if i move the Terminal from one Screen to the other and change focus to another window (it closes and reopens on the monitor on which my mouse is located at the time).
  WezTerm has no icon under Wayland when using fractional scaling (fractional-scale-v1) #6081
  I don't remember that happening in the last release, but i can not verify that anymore, because the current release is not starting anymore on my system.

• When using config.window_decorations = “RESIZE” with a high dpi screen, the client-side window decorations do not match the size of the terminal (at least with Gnome, which does not implement server-side window decorations). Also, every time the window loses or gains focus, the window changes size.
  Wezterm creates crazy large window on Wayland in Fedora 40 #5360. Also don't remember this happening in the last release.

[wez]

Thanks for commenting folks. From a triage perspective, what I care about here in the context of this issue is:

• Would releasing nightly now be worse than the prior stable release?

I don't want this issue to an umbrella for current bugs: those can all continue to live in the issue tracker.

So please review the comments you have made and if the issues are also present in the prior stable release, please edit your comments to elide that information from here.

I want to use this issue as a point of triage for getting wezterm-regressions-in-behavior-vs-its-last-stable-release resolved, and if it just duplicates general bugs it is not helpful.

Thank you!

[RomanAverin]

wezterm 20241031_235112_0983ae90
Fedora 41 - Gnome 47.1 - Mutter 47.1 - Wayland

• From what I feel the night version is a bit more stable(less crash), but in terms of UI it is a clear regression compared to the last release version 20240203_110809_5046fc22. Window resizing doesn't work in the night version as part of the regression.

config.animation_fps = 60
config.front_end = "WebGpu"
config.window_decorations = "INTEGRATED_BUTTONS"

[ateijelo]

Nightly fails to connect to an IPv6 link-local hostname that stable was connecting to successfully: #5934 (comment)

[Felixoid]

I am using Plasma 6 on arch linux, and have found so far two issues:

• An already mentioned Maximize is not working and fullscreen is not fullscreen #6203, and it looks a bit messy
• Annoying issue with moving wezterm window from one Wayland display to another Wezterm changes a window's size when moving from display to display #6374

[rlcurrall]

I used the nightly version on Windows 11 for about a week. I switched back to the stable release because my 1Password SSH integration wasn't working since the build wasn't signed in a way that Windows/1Password recognized.

During that time I didn't notice any regressions in functionality or performance (granted my configuration is pretty light). The main benefit of switching to the nightly for me was getting proper undercurl support so linting showed up in NeoVim. I'm currently using Windows Terminal while waiting for the next tagged release so I can use NeoVim and have linting work for me, but I'm eagerly awaiting a new release.

[NikSneMC]

Wezterm Nightly works fine for me on Hyprland 97a309b7844aea82b200139febc99998e7f06402 (NixOS) with Nvidia GPU

[otisdog8]

Wezterm 979df78 work for me on Hyprland a425fbebe4cf4238e48a42f724ef2208959d66cf with NixOS
Notably the currently released wezterm does not work with that config.

[Holmgren825]

Nightly crashes as soon as the window loose focus on river 0.3.5, see #6233. Current stable works as expected.

[akdor1154]

Pop 22.04 doesn't crash with default config, but pop's tiling doesn't seem to work (i'll raise separate issue - #6431).

[cguentherTUChemnitz]

tldr:
So from my side: a new release based on current main branch would be a great uplift against last release from February, even with known bugs, when running nixos gnome 47 wayland with fractional scaling.

long:
I there, i use nixos with gnome 47 in wayland with fractional scaling on a notebook, running with some already known bugs in the bugtracker. To come down to the main question of this thread:

Thanks for commenting folks. From a triage perspective, what I care about here in the context of this issue is:

* _Would releasing nightly now be worse than the prior stable release?_

Yes, i would highly love to see a current release, since i build wezterm at the moment explicitly from github master branch, which would solve for me the recompilation time ;) My current situation between master and latest release from February are:

• February release does not start in wayland mode with fractional scaling at all, or has completly broken textures for font rendering
• with current main i get at least a running instance, with some config setup also quite sharp font rendering despite fractional scaling, just the window resizing feels crazy and if have to do it with keyboard shortcuts. Also all wezterm windows are gone after going into lockscreen and coming back from it.

PS: config i use for current main:

        -- Your lua code / config here
       return {
         enable_wayland = true,
         font_size = 12.0,
         color_scheme = "Molokai",
         window_decorations = "TITLE | RESIZE",
         font = wezterm.font_with_fallback({
           { family = 'Fira Code' },
           { family = "Cambria Math", scale = 1.0 },
         })
       }

[g0r3]

WezTerm has no icon under Wayland when using fractional scaling (fractional-scale-v1) #6081
I don't remember that happening in the last release, but i can not verify that anymore, because the current release is not starting anymore on my system.

I was using wezterm 20240203.110809.5046fc22-2 from the Arch Linux repository, which corresponds to the latest wezterm release on the Github release page, and it doesn't have this issue. This problem appeared for me after compiling the git version of wezterm in order to solve a different problem. So this is very likely a regression. The current git version as of today is still affected.

[abhinavnatarajan]

Wezterm 20250103-160645-51886f4c works well for me on Wayland (cosmic-comp and Cosmic DE alpha 5 running on PopOS 24.04). The default configuration works without issue.

[g0r3]

Wezterm 20250103-160645-51886f4c works well for me on Wayland (cosmic-comp and Cosmic DE alpha 5 running on PopOS 24.04). The default configuration works without issue.

Cannot confirm this. I tried it mentioned version on Arch/KDE/Wayland and for me it has the same behavior regarding the icon.

[Noghpu]

The nightly version (WezTerm-windows-20250210-212000-f8921727) doesn't launch on my windows machine (10.0.18363 build 18363). Tried installing via scoop and the portable version.

The current release works fine.

Unfortunately I don't have the rights to update my Windows to see whether a different Windows 10 version would work

[bew]

@Noghpu Could you open a dedicated issue for this and fill up the issue template with your environment information?

[chenzhiwei]

Arch Linux, Wayland, KDE Plasma 6.3
WezTerm Config:

config.enable_scroll_bar = true
config.window_decorations = 'INTEGRATED_BUTTONS|RESIZE'
config.integrated_title_button_style = 'Windows'
config.integrated_title_buttons = {'Hide', 'Maximize', 'Close'}

• Nightly build, can't hide the title bar anymore, and the scrollbar width is small.

• Stable build(20240203-110809-5046fc22), works great.

[futile]

Let's just release at this point, and then fix stuff afterwards, then release again (like 1-2-3 weeks later maybe)? It seems like there has been quite some divergence, and that it's difficult to decide what's important enough to make it into this release?

Anyway, I guess what I actually was thinking about: I really liked this initiative to get a release out, but I feel like it has been stalling since October, so wanted to push it along :)

[wez]

@futile The reason I haven't made a release yet is because there are a significant number of cases where things are regressions, and I don't want to be under the gun to resolve them because someone was hasty about cutting a release. If you are not making a commitment to actively submit PRs to resolve those issues in that hypothetical 2 week time span, then you don't get to pressure for a release, or make comments about how it isn't moving fast enough for you.

If you are signing up to fix things up in 2 weeks, then I think that's great, but I'd rather spend the 2 weeks now, then cut the release once they are fixed.

[futile]

@futile The reason I haven't made a release yet is because there are a significant number of cases where things are regressions, and I don't want to be under the gun to resolve them because someone was hasty about cutting a release. If you are not making a commitment to actively submit PRs to resolve those issues in that hypothetical 2 week time span, then you don't get to pressure for a release, or make comments about how it isn't moving fast enough for you.

If you are signing up to fix things up in 2 weeks, then I think that's great, but I'd rather spend the 2 weeks now, then cut the release once they are fixed.

Got it, sorry for bothering you, that was unappropriate. Thanks for all your work on Wezterm!

[Felixoid]

The latest version from git crashes #6729, the version 20240203-110809-5046fc22 does not

[jhonfromerov]

Hi!
I don't know if this is useful yet, but here is my feedback:

System details:

• OS: Arch Linux x86_64
• Kernel: Linux 6.13.5-arch1-1
• Compositor: Hyprland 0.47.2-2
• Graphics server: Wayland 1.23.1-1

Last stable release (Wezterm 20240203.110809.5046fc22-2):

-Wezterm doesn't open from terminal (I try with ghostty and foot) or launcher (wofi 1.4.1-1).
-You have to apply a workaround like #5604 (comment).
-When it does open, Starship doesn't work.

Nightly (7d0bff0)

It works fine for me.

Thank you!

[Martin1887]

#6578 applies here.