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 678757 - DND tab to another window → critical warning or crash
DND tab to another window → critical warning or crash
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Accessibility
3.4.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2012-06-25 07:44 UTC by Josselin Mouette
Modified: 2018-04-14 23:59 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Josselin Mouette 2012-06-25 07:44:30 UTC 
Original report from 	Teodor MICU: http://bugs.debian.org/677508

“I can reproduce this problem by moving one tab between two g-t windows.
The tab to be moved had an 'man ps' process running. The tab is placed at
as the first tab on the second window. Moving this tab at the end (the last
or second tab in the window) and pressing an arrow key will kill it.”

I cannot reproduce the SIGSEGV but by trying to reproduce, scrolling in the moved tab behaves incorrectly, and I see a:
  GLib-GObject-CRITICAL **: g_object_notify: assertion `G_IS_OBJECT (object)' failed

Looking at the (incomplete) backtrace, it seems to me there is a remaining callback to an object that has been destroyed.

+ Trace 230421

  • #0 g_object_notify
    at /build/buildd-glib2.0_2.32.3-1-i386-987P8N/glib2.0-2.32.3/./gobject/gobject.c line 1154
  • #1 gtk_range_accessible_value_changed
    at /build/buildd-gtk+3.0_3.4.2-1-i386-sKVQ7r/gtk+3.0-3.4.2/./gtk/a11y/gtkrangeaccessible.c line 36
  • #2 g_cclosure_marshal_VOID__VOID
    at /build/buildd-glib2.0_2.32.3-1-i386-987P8N/glib2.0-2.32.3/./gobject/gmarshal.c line 85
  • #3 g_closure_invoke
    at /build/buildd-glib2.0_2.32.3-1-i386-987P8N/glib2.0-2.32.3/./gobject/gclosure.c line 777
  • #4 signal_emit_unlocked_R
    at /build/buildd-glib2.0_2.32.3-1-i386-987P8N/glib2.0-2.32.3/./gobject/gsignal.c line 3547
  • #5 g_signal_emit_valist
    at /build/buildd-glib2.0_2.32.3-1-i386-987P8N/glib2.0-2.32.3/./gobject/gsignal.c line 3296
  • #6 g_signal_emit
    at /build/buildd-glib2.0_2.32.3-1-i386-987P8N/glib2.0-2.32.3/./gobject/gsignal.c line 3352
  • #7 gtk_adjustment_value_changed
    at /build/buildd-gtk+3.0_3.4.2-1-i386-sKVQ7r/gtk+3.0-3.4.2/./gtk/gtkadjustment.c line 762
  • #8 gtk_adjustment_set_value
    at /build/buildd-gtk+3.0_3.4.2-1-i386-sKVQ7r/gtk+3.0-3.4.2/./gtk/gtkadjustment.c line 443
  • #9 ??
    from /usr/lib/libvte2_90.so.9
  • #10 ??
    from /usr/lib/libvte2_90.so.9
  • #11 ??
    from /usr/lib/libvte2_90.so.9
  • #12 ??
    from /usr/lib/libvte2_90.so.9
  • #13 ??
    from /usr/lib/libvte2_90.so.9
  • #14 g_timeout_dispatch
    at /build/buildd-glib2.0_2.32.3-1-i386-987P8N/glib2.0-2.32.3/./glib/gmain.c line 3882
  • #15 g_main_dispatch
    at /build/buildd-glib2.0_2.32.3-1-i386-987P8N/glib2.0-2.32.3/./glib/gmain.c line 2539
  • #16 g_main_context_dispatch
    at /build/buildd-glib2.0_2.32.3-1-i386-987P8N/glib2.0-2.32.3/./glib/gmain.c line 3075
  • #17 g_main_context_iterate
    at /build/buildd-glib2.0_2.32.3-1-i386-987P8N/glib2.0-2.32.3/./glib/gmain.c line 3146
  • #18 g_main_loop_run
    at /build/buildd-glib2.0_2.32.3-1-i386-987P8N/glib2.0-2.32.3/./glib/gmain.c line 3340
  • #19 gtk_main
    at /build/buildd-gtk+3.0_3.4.2-1-i386-sKVQ7r/gtk+3.0-3.4.2/./gtk/gtkmain.c line 1161
  • #20 ??
  • #21 __libc_start_main
    at libc-start.c line 228
  • #22 ?? 






Comment 1


Christian Persch





          2012-06-25 08:06:17 UTC
        



Looks like a problem in the gtk a11y code, re-assigning.






Comment 2


Josselin Mouette





          2012-06-25 08:17:23 UTC
        



In which case this might be related to bug#661521, although the conditions for reproducing look different.






Comment 3


Matthias Clasen





          2018-02-10 04:55:41 UTC
        



We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.






Comment 4


Matthias Clasen





          2018-04-14 23:59:45 UTC
        



As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla.

If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab:

https://gitlab.gnome.org/GNOME/gtk/issues/new