alacritty: [wayland-client error] Attempted to dispatch unknown opcode 0 for wl_shm, aborting.

Alacritty does not launch in Gnome on a wayland session. Works in Gnome X11 and in sway session on same machine.

OS: Fedora 33 Pre-Release Gnome: 3.37.90 Wayland: 1.18.0-2 Version: 0.5.0 and 0.6.0-dev commit 5ee7ae8a274fcc58754aa5a91a14b1dedbb87583

logs
> Output of: RUST_BACKTRACE=FULL WAYLAND_DEBUG=1 alacritty -vvv --print-events `
> [2394944.123]  -> wl_display@1.get_registry(new id wl_registry@2)
> [2394944.295]  -> wl_display@1.sync(new id wl_callback@3)
> [2394944.648] wl_display@1.delete_id(3)
> [2394944.760] wl_registry@2.global(1, "wl_drm", 2)
> [2394944.878] wl_registry@2.global(2, "wl_compositor", 4)
> [2394944.976]  -> wl_registry@2.bind(2, "wl_compositor", 4, new id [unknown]@4)
> [2394945.112] wl_registry@2.global(3, "wl_shm", 1)
> [2394945.203]  -> wl_registry@2.bind(3, "wl_shm", 1, new id [unknown]@5)
> [2394945.751] wl_registry@2.global(4, "wl_output", 2)
> [2394945.875]  -> wl_registry@2.bind(4, "wl_output", 2, new id [unknown]@6)
> [2394946.038] wl_registry@2.global(5, "zxdg_output_manager_v1", 3)
> [2394946.159] wl_registry@2.global(6, "wl_data_device_manager", 3)
> [2394946.263] wl_registry@2.global(7, "zwp_primary_selection_device_manager_v1", 1)
> [2394946.377] wl_registry@2.global(8, "gtk_primary_selection_device_manager", 1)
> [2394946.493] wl_registry@2.global(9, "wl_subcompositor", 1)
> [2394946.621] wl_registry@2.global(10, "xdg_wm_base", 3)
> [2394946.740] wl_registry@2.global(11, "zxdg_shell_v6", 1)
> [2394946.853] wl_registry@2.global(12, "wl_shell", 1)
> [2394946.971] wl_registry@2.global(13, "gtk_shell1", 3)
> [2394947.086] wl_registry@2.global(14, "wp_viewporter", 1)
> [2394947.204] wl_registry@2.global(15, "zwp_pointer_gestures_v1", 1)
> [2394947.299] wl_registry@2.global(16, "zwp_tablet_manager_v2", 1)
> [2394947.389] wl_registry@2.global(17, "wl_seat", 5)
> [2394947.518]  -> wl_registry@2.bind(17, "wl_seat", 5, new id [unknown]@7)
> [2394947.678] wl_registry@2.global(18, "zwp_relative_pointer_manager_v1", 1)
> [2394947.774]  -> wl_registry@2.bind(18, "zwp_relative_pointer_manager_v1", 1, new id [unknown]@8)
> [2394947.904] wl_registry@2.global(19, "zwp_pointer_constraints_v1", 1)
> [2394947.998]  -> wl_registry@2.bind(19, "zwp_pointer_constraints_v1", 1, new id [unknown]@9)
> [2394948.128] wl_registry@2.global(20, "zxdg_exporter_v1", 1)
> [2394948.220] wl_registry@2.global(21, "zxdg_importer_v1", 1)
> [2394948.311] wl_registry@2.global(22, "zwp_linux_dmabuf_v1", 3)
> [2394948.403] wl_registry@2.global(23, "zwp_keyboard_shortcuts_inhibit_manager_v1", 1)
> [2394948.506] wl_registry@2.global(24, "zwp_text_input_manager_v3", 1)
> [2394948.757] wl_registry@2.global(25, "gtk_text_input_manager", 1)
> [2394948.849] wl_callback@3.done(7585)
> [2394948.896]  -> wl_display@1.sync(new id wl_callback@3)
> [2394949.401] wl_display@1.delete_id(3)
> [2394949.502] wl_shm@5.format(0)
> [2394949.553] wl_shm@5.format(1)
> [2394949.602] wl_shm@5.format(909199186)
> [2394949.672] wl_shm@5.format(808669761)
> [2394949.720] wl_shm@5.format(808669784)
> [2394949.769] wl_shm@5.format(808665665)
> [2394949.817] wl_shm@5.format(808665688)
> [2394949.865] wl_shm@5.format(1211388481)
> [wayland-client error] Attempted to dispatch unknown opcode 0 for wl_shm, aborting.
</details>
stack trace

Message: Process 21749 (alacritty) of user 1000 dumped core.

            Stack trace of thread 21749:
            #0  0x00007f881894dbc5 raise (libc.so.6 + 0x3dbc5)
            #1  0x00007f88189368a4 abort (libc.so.6 + 0x268a4)
            #2  0x0000560b447dc50d _ZN14wayland_client3imp5proxy16proxy_dispatcher17h337ff8d0d37a0733E (alacritty + 0x1a750d)
            #3  0x00007f881853ef33 dispatch_event.isra.0 (libwayland-client.so.0 + 0x6f33)
            #4  0x00007f881853f19c wl_display_dispatch_queue_pending (libwayland-client.so.0 + 0x719c)
            #5  0x00007f88185416ef wl_display_roundtrip_queue (libwayland-client.so.0 + 0x96ef)
            #6  0x0000560b449e2b23 _ZN14wayland_client11event_queue10EventQueue14sync_roundtrip17h99b292052c928c16E (alacritty + 0x3adb23)
            #7  0x0000560b446fa61d _ZN22smithay_client_toolkit3env11Environment20from_display_with_cb17h27cf1234e65d2ffeE (alacritty + 0xc561d)
            #8  0x0000560b447c75f6 _ZN5winit13platform_impl8platform7wayland10event_loop18EventLoop$LT$T$GT$3new17h09c7387da55e48c6E (alacritty + 0x1925f6)
            #9  0x0000560b44745e1d _ZN9alacritty4main17h5d705b9366cf9fb5E (alacritty + 0x110e1d)
            #10 0x0000560b449c1e33 _ZN3std10sys_common9backtrace28__rust_begin_short_backtrace17h07251042be723e2aE (alacritty + 0x38ce33)
            #11 0x0000560b44745a2d main (alacritty + 0x110a2d)
            #12 0x00007f88189381a2 __libc_start_main (libc.so.6 + 0x281a2)
            #13 0x0000560b4469925e _start (alacritty + 0x6425e)

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Reactions: 8
  • Comments: 30 (21 by maintainers)

Commits related to this issue

Most upvoted comments

There’s a #4275 that should fix that issue.

Arch Linux package maintainer will wait for next release.

This bug makes the currently released version of Alacritty completely unusable on Gnome 3.38. As there is no timeline for 0.6.0 yet, please reconsider tagging 0.5.1.

Could we get a 0.5.1 tagged? Most distributions won’t pick it up otherwise, and with things like Fedora 33 and Ubuntu 20.10 coming which will ship with Gnome 3.38 it’ll be broken for a lot of folks.

Those distros are not shipping alacritty anyway, so you’re building it from source. If distro wants it can apply patch.

We will likely tag 0.6.0, but not sure how much time it’ll take us, since there’re still certain things that we should fix .

This bug makes the currently released version of Alacritty completely unusable on Gnome 3.38. As there is no timeline for 0.6.0 yet, please reconsider tagging 0.5.1.

Build from source, don’t see any issue with that.

Nah, nothing is required, just not sure if we’ll be able to pull changes in 0.5.1.