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 611039 - Dragging tabs still crash now and then in chat_window_update_chat_tab
Dragging tabs still crash now and then in chat_window_update_chat_tab
Status: RESOLVED DUPLICATE of bug 609929
Product: empathy
Classification: Core
Component: Chat
2.29.x
Other Linux
: Normal normal
: ---
Assigned To: empathy-maint
Depends on:
Blocks:
 
 
Reported: 2010-02-25 04:19 UTC by Diego Escalante Urrelo (not reading bugmail)
Modified: 2010-02-26 11:55 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Diego Escalante Urrelo (not reading bugmail) 2010-02-25 04:19:26 UTC
Trace:

Distribution: Debian squeeze/sid
Gnome Release: 2.29.92 2010-02-24 (JHBuild)
BugBuddy Version: 2.29.1

System: Linux 2.6.33-rc8 #1 SMP Mon Feb 22 05:02:20 PET 2010 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10705000
Selinux: No
Accessibility: Enabled
GTK+ Theme: StudioLooks
Icon Theme: gnome-brave
GTK+ Modules: gnomebreakpad, gail:atk-bridge, canberra-gtk-module

Memory status: size: 283131904 vsize: 283131904 resident: 66736128 share: 33382400 rss: 66736128 rss_rlim: 18446744073709551615
CPU usage: start_time: 1267069020 rtime: 8224 utime: 7788 stime: 436 cutime:22 cstime: 6 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/home/diego/gnome/build/bin/empathy'

[Thread debugging using libthread_db enabled]
[New Thread 0xabffeb70 (LWP 31046)]
[New Thread 0xac8ffb70 (LWP 31045)]
[New Thread 0xad2e1b70 (LWP 31043)]
[New Thread 0xb2105b70 (LWP 30895)]
0xb7703424 in __kernel_vsyscall ()

Thread 1 (Thread 0xb3f45780 (LWP 30850))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at gspawn.c line 386
  • #3 IA__g_spawn_command_line_sync
    at gspawn.c line 700
  • #4 run_bug_buddy
    at gnome-breakpad.cc line 369
  • #5 check_if_gdb
    at gnome-breakpad.cc line 440
  • #6 bugbuddy_segv_handle
    at gnome-breakpad.cc line 223
  • #7 <signal handler called>
  • #8 IA__gtk_widget_set_tooltip_markup
  • #9 chat_window_update_chat_tab
    at empathy-chat-window.c line 691
  • #10 chat_window_focus_in_event_cb
    at empathy-chat-window.c line 1527
  • #11 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 84
  • #12 IA__g_closure_invoke
    at gclosure.c line 767
  • #13 signal_emit_unlocked_R
    at gsignal.c line 3243
  • #14 IA__g_signal_emit_valist
    at gsignal.c line 2986
  • #15 IA__g_signal_emit
    at gsignal.c line 3033
  • #16 gtk_widget_event_internal
    at gtkwidget.c line 4941
  • #17 IA__gtk_main_do_event
    at gtkmain.c line 1601
  • #18 gdk_event_dispatch
    at gdkevents-x11.c line 2372
  • #19 g_main_dispatch
    at gmain.c line 1960
  • #20 IA__g_main_context_dispatch
    at gmain.c line 2513
  • #21 g_main_context_iterate
    at gmain.c line 2591
  • #22 IA__g_main_loop_run
    at gmain.c line 2799
  • #23 IA__gtk_main
    at gtkmain.c line 1219
  • #24 main
    at empathy.c line 690

Comment 1 Guillaume Desmottes 2010-02-26 09:12:13 UTC
Thanks for your bug report.
Do you have a scenario to easily reproduce this crash?
Comment 2 Diego Escalante Urrelo (not reading bugmail) 2010-02-26 09:23:13 UTC
1 Create two conversations.
2 Drag conv1 to conv2 window to make it tabbed.
3 Drag conv1 out.
4 Drag conv1 to conv2 window again.
5 Crash.

Further detail:
It seems that the crash happens when conv1 is attached to conv2 after *it has already been attached to it*.
So for example:
- I have A, B, C
- I open A, and B, separately
- I drag B into A
- Drag B out of A
- Drag B into A, again
- Crash
- Start empathy again
- Open A, and B
- Drag B into A
- Crash

Do you get the idea? Not sure if it's clear.

Btw this prints in the console, I think I didn't include it before:

(empathy:32603): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GtkImage'

(empathy:32603): Gtk-CRITICAL **: gtk_image_set_from_icon_name: assertion `GTK_IS_IMAGE (image)' failed

(empathy:32603): Gtk-CRITICAL **: gtk_widget_show: assertion `GTK_IS_WIDGET (widget)' failed
Comment 3 Guillaume Desmottes 2010-02-26 09:36:37 UTC
Thanks for these info. Could you retry using the GTK+ patch fixing bug #609929 please?
Comment 4 Diego Escalante Urrelo (not reading bugmail) 2010-02-26 10:16:17 UTC
Thanks Guillaume, that does the trick. I can't reproduce with the patch applied to gtk+ master.
Comment 5 Guillaume Desmottes 2010-02-26 11:55:51 UTC
Great; thanks for testing!

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 609929 ***