Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Input delay with corresponding ERROR log window::os::wayland::window > hide_cursor: Missing enter event serial #5760

Open
bonsairobo opened this issue Jun 27, 2024 · 3 comments · May be fixed by #6548
Open

Input delay with corresponding ERROR log window::os::wayland::window > hide_cursor: Missing enter event serial #5760

bonsairobo opened this issue Jun 27, 2024 · 3 comments · May be fixed by #6548
Labels
bug Something isn't working Wayland

Comments

@bonsairobo
Copy link

bonsairobo commented Jun 27, 2024 •
edited
Loading

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

Linux Wayland

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

KDE Plasma

WezTerm version

20240624-065522-552bb1d6

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

I started using the Wezterm nightly RPM on Bazzite, and I'm noticing significant, inconsistent input delay when typing. Then I tried spawning wezterm from a separate Konsole shell and noticed the following error on every key stroke:

$ wezterm start
18:36:56.401  ERROR  window::os::wayland::window > hide_cursor: Missing enter event serial
...

This log message seems like it was added a month ago. I don't know what it means or if it might be related to the input delay I'm experiencing.

To Reproduce

  1. Install Bazzite (ghcr.io/ublue-os/bazzite-nvidia:stable version 40.20240624.0 (2024-06-24T17:14:39Z)
  2. Install Wezterm: rpm-ostree install https://github.com/wez/wezterm/releases/download/nightly/wezterm-nightly-fedora40.rpm
  3. Reboot
  4. Launch Wezterm and start typing

Configuration

-- Pull in the wezterm API
local wezterm = require 'wezterm'

-- This table will hold the configuration.
local config = {}

-- In newer versions of wezterm, use the config_builder which will
-- help provide clearer error messages
if wezterm.config_builder then
  config = wezterm.config_builder()
end

config.font = wezterm.font 'JetBrainsMono Nerd Font'

config.color_scheme = 'catppuccin-mocha'

config.window_background_opacity = 0.95

config.hide_tab_bar_if_only_one_tab = true

return config

Expected Behavior

Responsive typing. This is what I'm used to from using Wezterm on NixOS.

Logs

wezterm version: 20240624-065522-552bb1d6 x86_64-unknown-linux-gnu
Window Environment: Wayland
Lua Version: Lua 5.4
OpenGL: NVIDIA GeForce GTX 1080/PCIe/SSE2 4.6.0 NVIDIA 550.90.07

Anything else?

No response
@bonsairobo bonsairobo added the bug Something isn't working label Jun 27, 2024
@wez wez added the Wayland label Jul 13, 2024
@fumiyas
Copy link
Contributor

fumiyas commented Nov 8, 2024

The same error message appears in the following environment, but after a few minutes (or something?) there is no error (why?).

WezTerm: 20241104-083404-51c794ac
OS: Debian GNU/Linux unstable (sid) amd64
Desktop: KDE 6.2.2 (Wayland)
IME: fcitx5 5.1.11-2
GPU: NVIDIA GeForce RTX 3050 Ti (driver version 545.23.06-1 from Debian experimental)

@Maxim4711
Copy link

Had the same issue, (fedora 41, wezterm-nigthly) - putting
config.enable_wayland = true into config file solved it

@jmbaur jmbaur linked a pull request Jan 3, 2025 that will close this issue
Open
@holmanb
Copy link

holmanb commented Jan 17, 2025 •
edited
Loading

significant, inconsistent input delay when typing

I see the same error log but don't experience any input delay.

OS: 24.10 - Ubuntu Oriole (current development release)
Build: source, latest commit on master (6c443be)
Toolchain: cargo 1.82.0
DE: GNOME
Wayland Compositor: Mutter

Launch Wezterm and start typing

This error is only logged when the cursor is not over the window. This means, for example, that if the window is opened full-screen, the cursor is likely to be over the window, which would prevent the issue from happening.

but after a few minutes (or something?) there is no error (why?).

Based on my testing, this log goes away when the cursor is moved over the window. Even moving the cursor off of the window does not cause the logs to reappear.

putting config.enable_wayland = true into config file solved it

The error log happens for me, but I have config.enable_wayland = true. I doubt that this is related.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working Wayland
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

wayland: prevent setting cursor when window is not focused jmbaur/wezterm
5 participants
@wez @fumiyas @bonsairobo @Maxim4711 @holmanb