On Thu, Mar 29, 2018 at 08:54:51PM +0100, Simon McVittie wrote: > Control: reassign -1 libgtk-3-0 3.22.29-2 > Control: forwarded -1 https://gitlab.gnome.org/GNOME/gtk/issues/129 > > On Thu, 29 Mar 2018 at 11:47:12 -0600, dann frazier wrote: > > affects 894388 + corebird > > This seems very unlikely to be a gnome-terminal bug if you also get it > for corebird. I'm guessing GDK or GTK+, which are in the same binary > package so it doesn't really matter which one has the bug. > > > #0 0x00007ffff2018e79 in wl_proxy_marshal (proxy=0x0, opcode=0) > > at ../src/wayland-client.c:692 > > #1 0x00007fffe2e461b9 in ?? () > > from /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-wayland.so > > Please could you retry this backtrace with libgtk-3-0-dbgsym installed?
Sure: (gdb) bt #0 0x00007ffff2018e79 in wl_proxy_marshal (proxy=proxy@entry=0x0, opcode=opcode@entry=0) at ../src/wayland-client.c:692 #1 0x00007fffe2e461b9 in gtk_text_input_destroy (gtk_text_input=0x0) at ../../../../../modules/input/gtk-text-input-client-protocol.h:498 #2 registry_handle_global_remove (data=0x555555e652d0, registry=<optimized out>, id=<optimized out>) at ../../../../../modules/input/imwayland.c:226 #3 0x00007fffef1e8fce in ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 #4 0x00007fffef1e893f in ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 #5 0x00007ffff201bd8b in wl_closure_invoke ( closure=closure@entry=0x555556e5f100, flags=flags@entry=1, target=<optimized out>, target@entry=0x555555e65310, opcode=opcode@entry=1, data=<optimized out>) at ../src/connection.c:935 #6 0x00007ffff2018928 in dispatch_event ( display=display@entry=0x555555b20ae0, queue=<optimized out>) at ../src/wayland-client.c:1310 #7 0x00007ffff2019be4 in dispatch_queue (queue=0x555555b20ba8, display=0x555555b20ae0) at ../src/wayland-client.c:1456 #8 wl_display_dispatch_queue_pending (display=0x555555b20ae0, queue=0x555555b20ba8) at ../src/wayland-client.c:1698 #9 0x00007ffff2019c3c in wl_display_dispatch_pending (display=<optimized out>) at ../src/wayland-client.c:1761 #10 0x00007ffff64e85c4 in _gdk_wayland_display_queue_events ( display=<optimized out>) at ../../../../../gdk/wayland/gdkeventsource.c:201 #11 0x00007ffff6488fc0 in gdk_display_get_event ( display=display@entry=0x555555b26110) at ../../../../gdk/gdkdisplay.c:438 #12 0x00007ffff64e82f2 in gdk_event_source_dispatch (base=<optimized out>, callback=<optimized out>, data=<optimized out>) at ../../../../../gdk/wayland/gdkeventsource.c:120 #13 0x00007ffff51ef287 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x00007ffff51ef4c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x00007ffff51ef54c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x00007ffff57afcbd in g_application_run () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #17 0x000055555556eb83 in _vala_main (args=<optimized out>, args_length1=<optimized out>) at main.c:50 #18 0x00007ffff4beca87 in __libc_start_main (main=0x55555556ea00 <main>, argc=1, argv=0x7fffffffe178, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffe168) at ../csu/libc-start.c:310 #19 0x000055555556ea3a in _start () > I can't say for sure from the backtrace without debug symbols, but this > looks a lot like <https://gitlab.gnome.org/GNOME/gtk/issues/114> (but we > thought we fixed that in 3.22.29-2) or > <https://gitlab.gnome.org/GNOME/gtk/issues/129> (which has a patch waiting > for review upstream). Let me know if you'd like me to test that, or any other patch. -dann