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

Weird issue when using wezterm on gnome wayland #6191

Open
NoahStoessel opened this issue Sep 24, 2024 · 0 comments
Open

Weird issue when using wezterm on gnome wayland #6191

NoahStoessel opened this issue Sep 24, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@NoahStoessel
Copy link

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

Linux Wayland

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

Mutter(AKA Gnome) version 47 wayland

WezTerm version

wezterm 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

Was installing wezterm with yay after hearing the hype to be then dissapointed when for some reason wezterm gave me this error
21:17:01.991 ERROR wezterm_gui > running message loop: Error while flushing display: Broken pipe (os error 32); terminating
warning: queue 0x62d63a011290 destroyed while proxies still attached:
wl_buffer#65 still attached
wl_buffer#66 still attached
wl_buffer#67 still attached
wl_buffer#68 still attached
wl_buffer#29 still attached
wl_buffer#44 still attached
wl_buffer#45 still attached
wl_buffer#47 still attached
wl_buffer#46 still attached
wl_buffer#42 still attached
wl_buffer#28 still attached
zwp_primary_selection_offer_v1#4278190081 still attached
wl_data_offer#4278190080 still attached
wl_subsurface#78 still attached
wl_surface#77 still attached
wl_subsurface#76 still attached
wl_surface#75 still attached
wl_subsurface#74 still attached
wl_surface#73 still attached
wl_subsurface#72 still attached
wl_surface#71 still attached
wl_subsurface#70 still attached
wl_surface#69 still attached
xdg_wm_base#21 still attached
wl_surface#20 still attached
wl_data_device#17 still attached
wl_pointer#15 still attached
zwp_text_input_v3#14 still attached
wl_keyboard#13 still attached
zwp_primary_selection_device_v1#12 still attached
zwp_primary_selection_device_manager_v1#3 still attached
wl_data_device#11 still attached
zwp_text_input_manager_v3#10 still attached
wl_seat#9 still attached
wl_subcompositor#8 still attached
wl_data_device_manager#7 still attached
wl_output#6 still attached
wl_shm#5 still attached
wl_compositor#4 still attached
wl_registry#2 still attached

No idea what it means but i know its related to wayland, have no tried nightly as yay doesnt have the nightly if i am not mistaken and im not about to deal with building from source with no available .tar.zst package in the releases, so yeah if someone can provide a nightly build cool but i aint dealing with debtap just or cargo just to get a nightly build

To Reproduce

command 1: yay -S wezterm
command 2: wezterm

Do this on gnome 47 wayland

Configuration

no config

Expected Behavior

just for wezterm to start

Logs

21:21:18.451 ERROR wezterm_gui > running message loop: error during event_q.dispatch protocol_error=Some(ProtocolError { code: 2, object_id: 44, object_interface: "wl_surface", message: "" }): Protocol error (os error 71); terminating

Anything else?

yeah maybe its cuz of gnome 47 or wayland idk

@NoahStoessel NoahStoessel added the bug Something isn't working label Sep 24, 2024
@dani162 dani162 mentioned this issue Nov 2, 2024
3 tasks
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