GNOME Bugzilla – Bug 538340
crash in Empathy Instant Messenger: switching Empathy to the...
Last modified: 2008-06-22 17:29:00 UTC
Version: 0.23.1 What were you doing when the application crashed? switching Empathy to the online status after resume Distribution: Fedora release 9 (Sulphur) Gnome Release: 2.22.2 2008-05-28 (Red Hat, Inc) BugBuddy Version: 2.22.0 System: Linux 2.6.25.4-30.fc9.i686 #1 SMP Wed May 21 18:12:35 EDT 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10499901 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Nodoka Icon Theme: Fedora Memory status: size: 53571584 vsize: 53571584 resident: 23502848 share: 13967360 rss: 23502848 rss_rlim: 4294967295 CPU usage: start_time: 1213422068 rtime: 997 utime: 889 stime: 108 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/empathy' [Thread debugging using libthread_db enabled] [New Thread 0xb8097950 (LWP 23490)] 0x00110416 in __kernel_vsyscall ()
+ Trace 200434
Thread 1 (Thread 0xb8097950 (LWP 23490))
----------- .xsession-errors --------------------- Could not find the frame base for "g_idle_dispatch". Could not find the frame base for "g_main_context_iterate". Could not find the frame base for "_tp_cli_connection_invoke_callback_for_new_channel". Could not find the frame base for "g_idle_dispatch". Could not find the frame base for "g_main_context_iterate". Could not find the frame base for "_tp_cli_connection_invoke_callback_for_new_channel". Could not find the frame base for "g_idle_dispatch". Could not find the frame base for "g_main_context_iterate". Could not find the frame base for "_tp_cli_connection_invoke_callback_for_new_channel". Could not find the frame base for "g_idle_dispatch". Could not find the frame base for "g_main_context_iterate". Could not find the frame base for "_tp_cli_connection_invoke_callback_for_new_channel". Could not find the frame base for "g_idle_dispatch". Could not find the frame base for "g_main_context_iterate". Could not find the frame base for "IA__g_spawn_sync". --------------------------------------------------
This may be caused by empathy_contact_get_id() returning NULL; empathy_contact_equal should probably guard against this. Digging further, in empathy_contact_set_name(), perhaps that line: contact_set_ready_flag (contact, EMPATHY_CONTACT_READY_NAME); should be called *after* priv->name has been set.
Hey hey, I just updated empathy after my little bug triaging session and this bug should be fixed now (r1180).