Bug#894388: affects corebird

2018-04-02 Thread dann frazier
On Sat, Mar 31, 2018 at 05:55:49PM +0100, Simon McVittie wrote:
> Control: forwarded -1 https://gitlab.gnome.org/GNOME/gtk/merge_requests/89
> 
> On Fri, 30 Mar 2018 at 11:45:31 -0600, dann frazier wrote:
> > #0  0x72018e79 in wl_proxy_marshal (proxy=proxy@entry=0x0, 
> > opcode=opcode@entry=0) at ../src/wayland-client.c:692
> > #1  0x7fffe2e461b9 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=0x55e652d0, 
> > registry=, id=)
> > at ../../../../../modules/input/imwayland.c:226
> 
> Thanks. Destroying a NULL struct gtk_text_input from
> registry_handle_global_remove() looks like
> https://gitlab.gnome.org/GNOME/gtk/issues/129#note_91002
> which looks like it would be addressed by
> https://gitlab.gnome.org/GNOME/gtk/merge_requests/89 which is awaiting
> upstream review.

Cool - fyi, I applied that patch locally and it does appear to solve
the problem.

 -dann



Bug#894388: affects corebird

2018-03-31 Thread Simon McVittie
Control: forwarded -1 https://gitlab.gnome.org/GNOME/gtk/merge_requests/89

On Fri, 30 Mar 2018 at 11:45:31 -0600, dann frazier wrote:
> #0  0x72018e79 in wl_proxy_marshal (proxy=proxy@entry=0x0, 
> opcode=opcode@entry=0) at ../src/wayland-client.c:692
> #1  0x7fffe2e461b9 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=0x55e652d0, 
> registry=, id=)
> at ../../../../../modules/input/imwayland.c:226

Thanks. Destroying a NULL struct gtk_text_input from
registry_handle_global_remove() looks like
https://gitlab.gnome.org/GNOME/gtk/issues/129#note_91002
which looks like it would be addressed by
https://gitlab.gnome.org/GNOME/gtk/merge_requests/89 which is awaiting
upstream review.

smcv



Bug#894388: affects corebird

2018-03-30 Thread dann frazier
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  0x72018e79 in wl_proxy_marshal (proxy=0x0, opcode=0)
> > at ../src/wayland-client.c:692
> > #1  0x7fffe2e461b9 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  0x72018e79 in wl_proxy_marshal (proxy=proxy@entry=0x0, 
opcode=opcode@entry=0) at ../src/wayland-client.c:692
#1  0x7fffe2e461b9 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=0x55e652d0, 
registry=, id=)
at ../../../../../modules/input/imwayland.c:226
#3  0x7fffef1e8fce in ffi_call_unix64 ()
   from /usr/lib/x86_64-linux-gnu/libffi.so.6
#4  0x7fffef1e893f in ffi_call ()
   from /usr/lib/x86_64-linux-gnu/libffi.so.6
#5  0x7201bd8b in wl_closure_invoke (
closure=closure@entry=0x56e5f100, flags=flags@entry=1, 
target=, target@entry=0x55e65310, 
opcode=opcode@entry=1, data=) at ../src/connection.c:935
#6  0x72018928 in dispatch_event (
display=display@entry=0x55b20ae0, queue=)
at ../src/wayland-client.c:1310
#7  0x72019be4 in dispatch_queue (queue=0x55b20ba8, 
display=0x55b20ae0) at ../src/wayland-client.c:1456
#8  wl_display_dispatch_queue_pending (display=0x55b20ae0, 
queue=0x55b20ba8) at ../src/wayland-client.c:1698
#9  0x72019c3c in wl_display_dispatch_pending (display=)
at ../src/wayland-client.c:1761
#10 0x764e85c4 in _gdk_wayland_display_queue_events (
display=) at ../../../../../gdk/wayland/gdkeventsource.c:201
#11 0x76488fc0 in gdk_display_get_event (
display=display@entry=0x55b26110) at ../../../../gdk/gdkdisplay.c:438
#12 0x764e82f2 in gdk_event_source_dispatch (base=, 
callback=, data=)
at ../../../../../gdk/wayland/gdkeventsource.c:120
#13 0x751ef287 in g_main_context_dispatch ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x751ef4c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x751ef54c in g_main_context_iteration ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x757afcbd in g_application_run ()
   from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#17 0x5556eb83 in _vala_main (args=, 
args_length1=) at main.c:50
#18 0x74beca87 in __libc_start_main (main=0x5556ea00 , 
argc=1, argv=0x7fffe178, init=, fini=, 
rtld_fini=, stack_end=0x7fffe168)
at ../csu/libc-start.c:310
#19 0x5556ea3a in _start ()

> I can't say for sure from the backtrace without debug symbols, but this
> looks a lot like  (but we
> thought we fixed that in 3.22.29-2) or
>  (which has a patch waiting
> for review upstream).

Let me know if you'd like me to test that, or any other patch.

   -dann



Bug#894388: affects corebird

2018-03-29 Thread Simon McVittie
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  0x72018e79 in wl_proxy_marshal (proxy=0x0, opcode=0)
> at ../src/wayland-client.c:692
> #1  0x7fffe2e461b9 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?

I can't say for sure from the backtrace without debug symbols, but this
looks a lot like  (but we
thought we fixed that in 3.22.29-2) or
 (which has a patch waiting
for review upstream).

smcv



Bug#894388: affects corebird

2018-03-29 Thread dann frazier
affects 894388 + corebird
thanks

corebird 1.7.4-1

(gdb) run
Starting program: /usr/bin/corebird 
[Thread debugging using libthread_db enabled]
[...]
(gdb) b
#0  0x72018e79 in wl_proxy_marshal (proxy=0x0, opcode=0)
at ../src/wayland-client.c:692
#1  0x7fffe2e461b9 in ?? ()
   from /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-wayland.so
#2  0x7fffef1e8fce in ffi_call_unix64 ()
   from /usr/lib/x86_64-linux-gnu/libffi.so.6
#3  0x7fffef1e893f in ffi_call ()
   from /usr/lib/x86_64-linux-gnu/libffi.so.6
#4  0x7201bd8b in wl_closure_invoke (
closure=closure@entry=0x56e9cb10, flags=flags@entry=1, 
target=, target@entry=0x55e62d60, 
opcode=opcode@entry=1, data=) at ../src/connection.c:935
#5  0x72018928 in dispatch_event (
display=display@entry=0x55b208d0, queue=)
at ../src/wayland-client.c:1310
#6  0x72019be4 in dispatch_queue (queue=0x55b20998, 
display=0x55b208d0) at ../src/wayland-client.c:1456
#7  wl_display_dispatch_queue_pending (display=0x55b208d0, 
queue=0x55b20998) at ../src/wayland-client.c:1698
#8  0x764e85c4 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#9  0x76488fc0 in gdk_display_get_event ()
   from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#10 0x764e82f2 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#11 0x751ef287 in g_main_context_dispatch ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x751ef4c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x751ef54c in g_main_context_iteration ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x757afcbd in g_application_run ()
   from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#15 0x5556eb83 in _vala_main (args=, 
args_length1=) at main.c:50
#16 0x74beca87 in __libc_start_main (main=0x5556ea00 , 
argc=1, argv=0x7fffe178, init=, fini=, 
rtld_fini=, stack_end=0x7fffe168)
at ../csu/libc-start.c:310
#17 0x5556ea3a in _start ()