After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 794736 - NULL pointer exception singal 11 (SEGV) in wl_proxy_marshal
NULL pointer exception singal 11 (SEGV) in wl_proxy_marshal
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Backend: Wayland
unspecified
Other Linux
: Normal critical
: ---
Assigned To: gtk-bugs
gtk-bugs
https://gitlab.gnome.org/GNOME/gtk/is...
Depends on:
Blocks:
 
 
Reported: 2018-03-27 17:00 UTC by Kai Lüke
Modified: 2018-03-29 08:55 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Kai Lüke 2018-03-27 17:00:12 UTC 
GNOME Terminal suddenly crashed when getting focused, see the proxy=0x0 problem. A similar bug was fixed in GTK recently:
https://gitlab.gnome.org/GNOME/gtk/issues/114

gdb: bt

+ Trace 238514

  • #0 wl_proxy_marshal
    at ../src/wayland-client.c line 692
  • #1 VteTerminalPrivate::im_update_cursor()
    at ../../src/vte.cc line 4504
  • #2 VteTerminalPrivate::process_incoming()
    at ../../src/vte.cc line 3898
  • #3 VteTerminalPrivate::time_process_incoming()
    at ../../src/vte.cc line 11053
  • #4 VteTerminalPrivate::process(bool)
    at ../../src/vte.cc line 11077
  • #5 update_timeout(gpointer)
    at ../../src/vte.cc line 11291
  • #6 g_timeout_dispatch
    at ../../../../glib/gmain.c line 4650
  • #7 g_main_dispatch
    at ../../../../glib/gmain.c line 3177
  • #8 g_main_context_dispatch
    at ../../../../glib/gmain.c line 3830
  • #9 g_main_context_iterate
    at ../../../../glib/gmain.c line 3903
  • #10 g_main_context_iteration
    at ../../../../glib/gmain.c line 3964
  • #11 g_application_run
    at ../../../../gio/gapplication.c line 2470
  • #12 0x000055d4f0053df2 in
  • #13 __libc_start_main
    at ../csu/libc-start.c line 310
  • #14 0x000055d4f0053e9a in
  • #0 wl_proxy_marshal
    at ../src/wayland-client.c line 692
  • #1 VteTerminalPrivate::im_update_cursor()
    at ../../src/vte.cc line 4504
  • #2 VteTerminalPrivate::process_incoming()
    at ../../src/vte.cc line 3898
  • #3 VteTerminalPrivate::time_process_incoming()
    at ../../src/vte.cc line 11053
  • #4 VteTerminalPrivate::process(bool)
    at ../../src/vte.cc line 11077
  • #5 update_timeout(gpointer)
    at ../../src/vte.cc line 11291
  • #6 g_timeout_dispatch
    at ../../../../glib/gmain.c line 4650
  • #7 g_main_dispatch
    at ../../../../glib/gmain.c line 3177
  • #8 g_main_context_dispatch
    at ../../../../glib/gmain.c line 3830
  • #9 g_main_context_iterate
    at ../../../../glib/gmain.c line 3903
  • #10 g_main_context_iteration
    at ../../../../glib/gmain.c line 3964
  • #11 g_application_run
    at ../../../../gio/gapplication.c line 2470
  • #12 0x000055d4f0053df2 in
  • #13 __libc_start_main
    at ../csu/libc-start.c line 310
  • #14 0x000055d4f0053e9a in 






Comment 1


Christian Persch





          2018-03-27 17:09:16 UTC
        



That's crashing inside the call to gtk_im_context_set_cursor_location(m_im_context, &rect); re-assigning to gtk+:wayland.






Comment 2


Kai Lüke





          2018-03-28 02:27:21 UTC
        



Was running this version where some of the last patches are already included regarding wayland. But maybe it has been fixed on master?

gtk+3.0 (3.22.29-2) unstable; urgency=medium

  * Team upload
  * Refresh patch series through gbp-pq
    - Harvest date and authorship information from debian/changelog
  * Add more upstream status information to the patch series
  * d/p/0009-gtkimmodule-make-match_backend-query-the-wayland-reg.patch,
    d/p/0010-imwayland-Avoid-TOGGLE_INPUT_PANEL-requests-if-there.patch:
    Add patches from upstream fixing Wayland client crashes under
    unspecified circumstances (Closes: #893696)
  * d/p/0011-gtkstylecontext-guard-against-gtk_css_widget_node_ge.patch:
    Add patch from upstream fixing a NULL dereference
  * d/p/0012-widget-Only-print-allocation-warnings-with-enable-de.patch:
    Add patch from upstream silencing allocation warnings for stable
    branches (if there is ever a GTK+ 3.23 then these warnings would
    come back until 3.24). (Closes: #867427)

 -- Simon McVittie <smcv@debian.org>  Thu, 22 Mar 2018 10:15:24 +0000






Comment 3


Daniel Boles





          2018-03-28 10:10:23 UTC
        



this is probably https://gitlab.gnome.org/GNOME/gtk/issues/129