-
-
Notifications
You must be signed in to change notification settings - Fork 786
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
Consistent crash when opening new terminal window (wayland) #5311
Comments
I am also getting protocol error 2 when spawning a new window. I am launching with a gnome shell global shortcut. It happens every time if a wezterm window has the focus, but does not happen if a different application's window has focus. I see the error pop up as a gnome shell notification with title "Wezterm Error" and body "running message loop: Protocol error 2 on object wl_surface@27:". The number is not the same each time. Here's a screenshot: This looks like the same issue to me, but perhaps someone else can verify this, or otherwise. |
Duplicate of #5103 |
Duplicate of #5103 |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
What Operating System(s) are you seeing this problem on?
Linux Wayland
Which Wayland compositor or X11 Window manager(s) are you using?
river
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
I have a binding to spawn a new terminal in the CWD:
This binding consistently crashes wezterm with the following error:
WezTerm also crashes when spawning a new terminal with an external (compositor) key binding. In this case though, it spawns one additional terminal successfully before crashing. The error is the same.
To Reproduce
No response
Configuration
Expected Behavior
No response
Logs
15:03:05.513 WARN wezterm_gui::termwindow::resize > cannot resize window to match Some(RowsAndCols { rows: 52, cols: 226 }) because window_state is MAXIMIZED
15:03:05.786 ERROR wezterm_mux_server_impl::local > writing pdu data buffer: Broken pipe (os error 32)
15:03:05.794 WARN wezterm_gui::termwindow::resize > cannot resize window to match Some(RowsAndCols { rows: 52, cols: 146 }) because window_state is MAXIMIZED
15:03:27.510 ERROR wezterm_mux_server_impl::local > writing pdu data buffer: Broken pipe (os error 32)
15:07:19.029 ERROR wezterm_mux_server_impl::local > writing pdu data buffer: Broken pipe (os error 32)
15:07:19.038 WARN wezterm_gui::termwindow::resize > cannot resize window to match Some(RowsAndCols { rows: 52, cols: 226 }) because window_state is MAXIMIZED
15:11:44.819 ERROR wezterm_mux_server_impl::local > writing pdu data buffer: Broken pipe (os error 32)
Anything else?
No response
The text was updated successfully, but these errors were encountered: