wezterm doesn't redraw (or lags) on Plasma 6 + Wayland + Nvidia with config.enable_wayland=true

[braxtons12]

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

Linux Wayland

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

KWin 6 w/ Plasma Renderer settings set as: Rendering Backend: OpenGL Render Loop: Basic GL Core Profile: [ ]

WezTerm version

wezterm 20240405-180910-cce0706b

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

Intermittently wezterm will fail to redraw/re-render/refresh itself until I move my mouse over/within the window on the combination of Plasma 6 + Wayland + Nvidia (I previously did not have this issue on Plasma 5 + X11 + Nvidia).

I notice this issue the most when using Neovim, but I've encountered it when running general CLI apps (e.g. Paru, npm)

To Reproduce

1. Open Wezterm
2. Do any of: 2.a. Open a file in neovim then do something (preferably a command that only takes 1 keystroke but causes UI interaction) 2.b. Run a CLI command that generates a non-trivial amount of output 2.c. Open a large file in neovim and just hold j or k down.
3. No visual update, or seconds for the update to happen (i.e. not profit)

Configuration

I don't think this is config dependent, but here you go https://github.com/braxtons12/dotfiles/blob/master/.config/wezterm/wezterm.lua

Expected Behavior

wezterm redraws as expected

Logs

Debug Overlay wezterm version: 20240405-180910-cce0706b x86_64-unknown-linux-gnu Window Environment: Wayland Lua Version: Lua 5.4 OpenGL: NVIDIA GeForce RTX 4080/PCIe/SSE2 4.6.0 NVIDIA 550.67 Enter lua statements or expressions and hit Enter. Press ESC or CTRL-D to exit 22:11:56.890 ERROR window::os::wayland::window > set_cursor: Cursor not found 22:11:58.150 ERROR window::os::wayland::window > set_cursor: Cursor not found 22:11:58.692 ERROR window::os::wayland::window > set_cursor: Cursor not found 22:12:00.151 ERROR window::os::wayland::window > set_cursor: Cursor not found 22:12:00.749 ERROR window::os::wayland::window > set_cursor: Cursor not found

Anything else?

This can be really hard to reproduce with general usage, but the "just hold j down" approach is pretty consistent. With general usage, there doesn't seem to be any rhyme or reason to the (in)consistency of it, though. Anecdotally, it seems more likely to happen in the first instance of wezterm I've opened since booting the OS, but I can't say for sure if that's actually the case (I haven't actually tracked it).

[wez]

Could you try the most recently nightly build?

[SamWindell]

I've had this exact same issue. I'm also using Wayland + Nvidia, but Hyprland instead of Plasma.

[braxtons12]

@wez I haven't had enough time doing development at home over the last few weeks to be 100% sure (it's possible I just haven't ran into it), but I do believe this is fixed now.

[SuperSandro2000]

I've run into the same issue and sadly disabling wayland fixed the issue for me.

[chairbender]

Same issue on Wayland + Nvidia + Hyprland, on the latest (as of today) commit. Disabling wayland "fixes" it.