-
-
Notifications
You must be signed in to change notification settings - Fork 794
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
Weztem crashing on text selection #6128
Comments
Hi Brayan, So you're actually using X11 rather than Wayland with that variable set to false. But EDIT: sorry, that PR is indeed only addressing a Wayland bug, so can't be the problem you're seeing. If you run: WEZTERM_LOG=trace wezterm and capture the output, it may reveal right where things are going wrong. |
Hey Brayan, After looking at it a bit more, it appears you're running out of memory. Judging from the selection text, you're operating in a container of some type?
But the error is essentially "XCB connection closed, insufficient memory". |
Capturing the output of And no, I am not on a container or emulator of any kind, I am using EndevourOS on an hp laptop. Having said all of that, I think the problem started after I installed
|
Hi, Thanks for all the good info. I see you filed a report with wl-clip-persist too, and they have Would you be able to test the small patch to see if it helps? It's in the "clip-persist" branch It shouldn't crash, but it's not totally clear if copy/paste will continue to work afterward. |
It works! |
There are situations where transient xcb errors can be generated in regard to copy/paste selection. One example was reported in connection with "wl-clip-persist" in issue wez#6128. And another in issue wez#5482. But there's no reason for us to commit harakiri in response, so just quietly ignore such errors.
There are situations where transient xcb errors can be generated in regard to copy/paste selection. One example was reported in connection with "wl-clip-persist" in issue wez#6128. And another in issue wez#5482. But there's no reason for us to terminate in response, so just quietly ignore such errors.
There are situations where transient xcb errors can be generated in regard to copy/paste selection. One example was reported in connection with "wl-clip-persist" in issue wez#6128. And another in issue wez#5482. But there's no reason for us to terminate in response, so catch and report any selection-related errors, as per code review in PR wez#6135
There are situations where transient xcb errors can be generated in regard to copy/paste selection. One example was reported in connection with "wl-clip-persist" in issue #6128. And another in issue #5482. But there's no reason for us to terminate in response, so catch and report any selection-related errors, as per code review in PR #6135
This should be resolved now in It typically takes about an hour before commits are available as nightly builds for all platforms. Linux builds are the fastest to build and are often available within about 20 minutes. Windows and macOS builds take a bit longer. Please take a few moments to try out the fix and let me know how that works out. You can find the nightly downloads for your system in the wezterm installation docs. If you prefer to use packages provided by your distribution or package manager of choice and don't want to replace that with a nightly download, keep in mind that you can download portable packages (eg: a If you are eager and can build from source then you may be able to try this out more quickly. |
What Operating System(s) are you seeing this problem on?
Linux Wayland
Which Wayland compositor or X11 Window manager(s) are you using?
I am using Hyprland and have
config.enable_wayland = false
in my config because I was experience other issues if set to true. I never encountered this problem before in this machine so I am not sure what is going on.WezTerm version
wezterm 20240203.110809.5046fc22-2
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
On my laptop, if I start selecting and keep selecting text on wezterm, during that time all is good. But as soon as I let go of the track-pad, wezterm crashes with the following error.
To Reproduce
No response
Configuration
config.enable_wayland = false
Expected Behavior
No response
Logs
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: