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

Consistent crash when opening new terminal window (wayland) #5311

Closed
cmvanb opened this issue Apr 17, 2024 · 4 comments
Closed

Consistent crash when opening new terminal window (wayland) #5311

cmvanb opened this issue Apr 17, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@cmvanb
Copy link

cmvanb commented Apr 17, 2024

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:

        {
            key = 't',
            mods = 'CTRL',
            action = wezterm.action.SpawnWindow,
        },

This binding consistently crashes wezterm with the following error:

Wezterm Error
running message loop: error during event_q.dispatch protocol_error=Some(ProtocolError { code: 2, object_id: 80, object_interface: "wl_surface", message: "" }): Protocol error (os error 71)

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

        {
            key = 't',
            mods = 'CTRL',
            action = wezterm.action.SpawnWindow,
        },

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

@cmvanb cmvanb added the bug Something isn't working label Apr 17, 2024
@jamespharaoh
Copy link

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:

Screenshot from 2024-04-18 16-29-53

This looks like the same issue to me, but perhaps someone else can verify this, or otherwise.

@woojiq
Copy link

woojiq commented Apr 19, 2024

Duplicate of #5103

@wez
Copy link
Owner

wez commented May 5, 2024

Duplicate of #5103

@wez wez marked this as a duplicate of #5103 May 5, 2024
@wez wez closed this as completed May 5, 2024
Copy link
Contributor

github-actions bot commented Jun 5, 2024

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 5, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants