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 636228 - critical warning when clicking on a contact on the contact list
critical warning when clicking on a contact on the contact list
Status: RESOLVED DUPLICATE of bug 627813
Product: empathy
Classification: Core
Component: Meta Contacts
2.91.x
Other Linux
: Normal normal
: ---
Assigned To: empathy-maint
Depends on:
Blocks:
 
 
Reported: 2010-12-01 15:50 UTC by Emilio Pozuelo Monfort
Modified: 2011-08-29 10:12 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Emilio Pozuelo Monfort 2010-12-01 15:50:08 UTC 
When clicking on a contact after launching empathy, I get this assertion. It seems to only happen once, i.e. the first time I click on a contact I get it, but if then I click on another, I don't.

Gtk-CRITICAL **: gtk_tree_model_filter_real_unref_node: assertion `elt->ref_count > 0' failed
aborting...

Program received signal SIGTRAP, Trace/breakpoint trap.
g_logv (log_domain=<value optimized out>, log_level=<value optimized out>, format=<value optimized out>, 
    args1=0x7fffffffdc80) at /tmp/buildd/glib2.0-2.27.4/glib/gmessages.c:563
563	/tmp/buildd/glib2.0-2.27.4/glib/gmessages.c: No such file or directory.
	in /tmp/buildd/glib2.0-2.27.4/glib/gmessages.c
(gdb) bt

+ Trace 224924

  • #0 g_logv
    at /tmp/buildd/glib2.0-2.27.4/glib/gmessages.c line 563
  • #1 g_log
    at /tmp/buildd/glib2.0-2.27.4/glib/gmessages.c line 577
  • #2 gtk_tree_model_filter_real_unref_node
    at /tmp/buildd/gtk+3.0-2.91.5/gtk/gtktreemodelfilter.c line 2823
  • #3 gtk_tree_row_reference_unref_path
    at /tmp/buildd/gtk+3.0-2.91.5/gtk/gtktreemodel.c line 1879
  • #4 gtk_tree_row_reference_free
    at /tmp/buildd/gtk+3.0-2.91.5/gtk/gtktreemodel.c line 2105
  • #5 gtk_tree_view_real_set_cursor
    at /tmp/buildd/gtk+3.0-2.91.5/gtk/gtktreeview.c line 12723
  • #6 gtk_tree_view_button_press
    at /tmp/buildd/gtk+3.0-2.91.5/gtk/gtktreeview.c line 2916
  • #7 _gtk_marshal_BOOLEAN__BOXED
    at /tmp/buildd/gtk+3.0-2.91.5/gtk/gtkmarshalers.c line 85
  • #8 g_closure_invoke
    at /tmp/buildd/glib2.0-2.27.4/gobject/gclosure.c line 766
  • #9 signal_emit_unlocked_R
    at /tmp/buildd/glib2.0-2.27.4/gobject/gsignal.c line 3290
  • #10 g_signal_emit_valist
    at /tmp/buildd/glib2.0-2.27.4/gobject/gsignal.c line 2993
  • #11 g_signal_emit
    at /tmp/buildd/glib2.0-2.27.4/gobject/gsignal.c line 3040
  • #12 gtk_widget_event_internal
    at /tmp/buildd/gtk+3.0-2.91.5/gtk/gtkwidget.c line 5844
  • #13 gtk_propagate_event
    at /tmp/buildd/gtk+3.0-2.91.5/gtk/gtkmain.c line 2503
  • #14 gtk_main_do_event
    at /tmp/buildd/gtk+3.0-2.91.5/gtk/gtkmain.c line 1729
  • #15 gdk_event_source_dispatch
    at /tmp/buildd/gtk+3.0-2.91.5/gdk/x11/gdkeventsource.c line 323
  • #16 g_main_dispatch
    at /tmp/buildd/glib2.0-2.27.4/glib/gmain.c line 2436
  • #17 g_main_context_dispatch
    at /tmp/buildd/glib2.0-2.27.4/glib/gmain.c line 3009
  • #18 g_main_context_iterate
    at /tmp/buildd/glib2.0-2.27.4/glib/gmain.c line 3087
  • #19 g_main_loop_run
    at /tmp/buildd/glib2.0-2.27.4/glib/gmain.c line 3295
  • #20 gtk_main
    at /tmp/buildd/gtk+3.0-2.91.5/gtk/gtkmain.c line 1297
  • #21 g_application_run
    at /tmp/buildd/glib2.0-2.27.4/gio/gapplication.c line 1216
  • #22 main
    at empathy.c line 725 






Comment 1


Guillaume Desmottes





          2010-12-02 10:03:53 UTC
        



I tought we already have a bug opened for this one but can't find it, so I guess I was wrong.

This error has bene introduced with folks. I think Philip and/or Travis spent time trying to debug it but didn't manage to find the source of the issue.






Comment 2


Philip Withnall





          2010-12-02 11:17:28 UTC
        



It's a combination of bug #626552 and bug #621076, which is explained in bug #627813.

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 627813 ***






Comment 3


Guillaume Desmottes





          2010-12-02 11:29:33 UTC
        



Ah thanks, I didn't manage to find these bugs. :)