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 661521 - gnome-terminal crashed with SIGSEGV in g_object_notify()
gnome-terminal crashed with SIGSEGV in g_object_notify()
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Accessibility
3.2.x
Other Linux
: Normal critical
: ---
Assigned To: gtk-bugs
gtk-bugs
: 685247 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-10-12 07:16 UTC by Dmitry Shachnev
Modified: 2016-01-17 21:30 UTC
See Also:
GNOME target: ---
GNOME version: 3.1/3.2


Description Dmitry Shachnev 2011-10-12 07:16:06 UTC 
This bug report has been filed here:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/864813

STACKTRACE:

+ Trace 228758

  • #0 g_object_notify
    at /build/buildd/glib2.0-2.30.0/./gobject/gobject.c line 1003
  • #1 gtk_range_accessible_value_changed
    at /build/buildd/gtk+3.0-3.2.0/./gtk/a11y/gtkrangeaccessible.c line 38
  • #2 g_cclosure_marshal_VOID__VOID
    at /build/buildd/glib2.0-2.30.0/./gobject/gmarshal.c line 85
  • #3 g_closure_invoke
    at /build/buildd/glib2.0-2.30.0/./gobject/gclosure.c line 774
  • #4 signal_emit_unlocked_R
    at /build/buildd/glib2.0-2.30.0/./gobject/gsignal.c line 3272
  • #5 g_signal_emit_valist
    at /build/buildd/glib2.0-2.30.0/./gobject/gsignal.c line 3003
  • #6 g_signal_emit
    at /build/buildd/glib2.0-2.30.0/./gobject/gsignal.c line 3060
  • #7 gtk_adjustment_value_changed
    at /build/buildd/gtk+3.0-3.2.0/./gtk/gtkadjustment.c line 764
  • #8 gtk_adjustment_set_value
    at /build/buildd/gtk+3.0-3.2.0/./gtk/gtkadjustment.c line 445
  • #9 vte_terminal_emit_adjustment_changed
    at /build/buildd/vte-0.28.2/./src/vte.c line 2067
  • #10 vte_terminal_emit_pending_signals
    at /build/buildd/vte-0.28.2/./src/vte.c line 14797
  • #11 vte_terminal_process_incoming
    at /build/buildd/vte-0.28.2/./src/vte.c line 4419
  • #12 time_process_incoming
    at /build/buildd/vte-0.28.2/./src/vte.c line 14839
  • #13 process_timeout
    at /build/buildd/vte-0.28.2/./src/vte.c line 14886
  • #14 g_timeout_dispatch
    at /build/buildd/glib2.0-2.30.0/./glib/gmain.c line 3907
  • #15 g_main_dispatch
    at /build/buildd/glib2.0-2.30.0/./glib/gmain.c line 2441
  • #16 g_main_context_dispatch
    at /build/buildd/glib2.0-2.30.0/./glib/gmain.c line 3011
  • #17 g_main_context_iterate
    at /build/buildd/glib2.0-2.30.0/./glib/gmain.c line 3089
  • #18 g_main_loop_run
    at /build/buildd/glib2.0-2.30.0/./glib/gmain.c line 3297
  • #19 gtk_main
    at /build/buildd/gtk+3.0-3.2.0/./gtk/gtkmain.c line 1367
  • #20 main
    at terminal.c line 594 






Comment 1


Christian Persch





          2011-10-12 14:49:18 UTC
        



You need to use vte 0.30 with gtk 3.2, while ubuntu only has 0.28.

If the same were to happen with 0.30, it would be either a bug in the gtk a11y impl, or in vte's.






Comment 2


Dmitry Shachnev





          2011-10-12 15:06:53 UTC
        



Ubuntu has a patch backported from 0.30 for gtk 3.2 support: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/oneiric/vte/oneiric/revision/118.

Reopening for gtk+.






Comment 3


Matthias Clasen





          2011-10-13 17:48:34 UTC
        



crash in a11y






Comment 4


Fabio Durán Verdugo





          2012-10-01 20:29:12 UTC
        



*** Bug 685247 has been marked as a duplicate of this bug. ***






Comment 5


Matthias Clasen





          2016-01-16 19:49:47 UTC
        



I don't think this is relevant anymore