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.

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

Wezterm *occasionally* interprets single clicks as double clicks (or triple lcicks #6435

Open
moonpiedumplings opened this issue Nov 25, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@moonpiedumplings
Copy link

moonpiedumplings commented Nov 25, 2024

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

Linux Wayland

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

KDE with Wayland, so KWin.

Also, it might be relevant that I have an Nvidia GPU.

WezTerm version

20240203-110809-5046fc22

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

Occasionally, wezterm interprets a single click as a double click. Or a triple click. I have attatched a video where it interprets single clicks as double clicks, and also copies anything that is "double clicked" and selected to the clipboard (which also, doesn't always happen).

weztermbug.webm

To Reproduce

I cannot figure out what triggers this behavior, sadly, it appears to be inconsistent. Wezterm always begins by working perfectly though, which makes me think that some action I take on my system elsewhere breaks things.

I suspect that maybe fullscreening other apps, like games is what causes the breakage but I couldn't get it to reliably trigger.

I also tested with the nightly wezterm appimage, wezterm 20241119-101432-4050072d, but I couldn't trigger the bug, at least not in one night. I'll switch to the appimage as my main terminal and see if I can trigger it and update this issue accordingly if that happens.

Configuration

No config (unless Arch/CachyOS changes some configs I couldn't find)

Expected Behavior

Single clicks should be single clicks.

Logs

Debug Overlay
wezterm version: 20240203-110809-5046fc22 x86_64-unknown-linux-gnu
Window Environment: Wayland
Lua Version: Lua 5.4
OpenGL: AMD Radeon Graphics (radeonsi, renoir, LLVM 18.1.8, DRM 3.59, 6.11.6-zen1-1-zen) 4.6 (Compatibility Profile) Mesa 24.2.6-cachyos1.3
Enter lua statements or expressions and hit Enter.
Press ESC or CTRL-D to exit
22:17:23.553 WARN wezterm_ssh::pty > ssh: setenv TERM_PROGRAM_VERSION=20240203-110809-5046fc22 failed: RequestDenied: Channel request env failed. Check the AcceptEnv setting on the ssh server side. Additional errors with setting env vars in this session will be logged at debug log level.
22:17:24.600 ERROR window::os::wayland::pointer > set_cursor: Unable to set cursor to hand: cursor not found
22:17:24.602 ERROR window::os::wayland::pointer > set_cursor: Unable to set cursor to hand: cursor not found
22:17:24.603 ERROR window::os::wayland::pointer > set_cursor: Unable to set cursor to hand: cursor not found
22:18:53.247 ERROR wezterm_gui::termwindow::palette > Error while saving recents: No such file or directory (os error 2)
22:19:01.271 ERROR wezterm_gui::termwindow::palette > Error while saving recents: No such file or directory (os error 2)

Anything else?

Zellij appears to be unaffected by this bug, when I run it inside of a bugged wezterm.

Also, I really hope this is a duplicate of another issue.

@moonpiedumplings moonpiedumplings added the bug Something isn't working label Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant