Bug 447578 – crash in Empathy Instant Messenger: creating a new account

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 447578 - crash in Empathy Instant Messenger: creating a new account


Summary:	crash in Empathy Instant Messenger: creating a new account


Status:	RESOLVED NOTGNOME

Product:	empathy
Classification:	Core
Component:	General
Version:	0.7
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	empathy-maint
QA Contact:	empathy-maint

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-06-14 15:48 UTC by Steven Garrity
Modified:	2007-06-14 16:55 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description Steven Garrity 2007-06-14 15:48:55 UTC

What were you doing when the application crashed?
creating a new account


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: MurrinaGilouche
Icon Theme: Tango

Memory status: size: 97464320 vsize: 97464320 resident: 34136064 share: 30580736 rss: 34136064 rss_rlim: 4294967295
CPU usage: start_time: 1181836104 rtime: 27 utime: 23 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/empathy'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208740128 (LWP 6553)]
(no debugging symbols found)
0x00fe2402 in __kernel_vsyscall ()

+ Trace 140966

Thread 1 (Thread -1208740128 (LWP 6553))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 mc_protocol_get_params
from /usr/lib/libmissioncontrol-config.so.0
#5 mc_profile_get_default_setting
from /usr/lib/libmissioncontrol-config.so.0
#6 mc_account_get_param_int
from /usr/lib/libmissioncontrol-config.so.0
#7 gossip_account_widget_jabber_new
#8 ??
#9 ??
#10 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#11 g_closure_invoke
from /lib/libgobject-2.0.so.0
#12 ??
from /lib/libgobject-2.0.so.0
#13 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#14 g_signal_emit
from /lib/libgobject-2.0.so.0
#15 ??
from /usr/lib/libgtk-x11-2.0.so.0
#16 gtk_tree_selection_select_path
from /usr/lib/libgtk-x11-2.0.so.0
#17 gtk_tree_selection_select_iter
from /usr/lib/libgtk-x11-2.0.so.0
#18 ??
#19 ??
#20 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#21 g_closure_invoke
from /lib/libgobject-2.0.so.0
#22 ??
from /lib/libgobject-2.0.so.0
#23 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#24 g_signal_emit
from /lib/libgobject-2.0.so.0
#25 gtk_button_clicked
from /usr/lib/libgtk-x11-2.0.so.0
#26 ??
from /usr/lib/libgtk-x11-2.0.so.0
#27 ??
from /usr/lib/libgtk-x11-2.0.so.0
#28 ??
from /usr/lib/libgtk-x11-2.0.so.0
#29 ??
from /lib/libgobject-2.0.so.0
#30 g_closure_invoke
from /lib/libgobject-2.0.so.0
#31 ??
from /lib/libgobject-2.0.so.0
#32 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#33 g_signal_emit
from /lib/libgobject-2.0.so.0
#34 ??
from /usr/lib/libgtk-x11-2.0.so.0
#35 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#36 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#37 ??
from /usr/lib/libgdk-x11-2.0.so.0
#38 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#39 ??
from /lib/libglib-2.0.so.0
#40 g_main_loop_run
from /lib/libglib-2.0.so.0
#41 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#42 main
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
** (empathy:6553): CRITICAL **: mc_profile_get_protocol: assertion `manager != NULL' failed
** (empathy:6553): CRITICAL **: mc_profile_get_protocol: assertion `manager != NULL' failed
** (empathy:6553): DEBUG: mission_control_get_presence_actual: MC not running.
** (empathy:6553): DEBUG: check_for_accounts: No enabled accounts
** (empathy:6553): DEBUG: mission_control_get_presence_actual: MC not running.
** (empathy:6553): DEBUG: mission_control_get_presence_message_actual: MC not running.
** (empathy:6553): DEBUG: check_for_accounts: No enabled accounts
** (empathy:6553): DEBUG: mission_control_get_presence_actual: MC not running.
** (empathy:6553): DEBUG: mission_control_get_presence_message_actual: MC not running.
** (empathy:6553): DEBUG: check_for_accounts: No enabled accounts
** (empathy:6553): CRITICAL **: mc_profile_get_protocol: assertion `manager != NULL' failed
--------------------------------------------------

Comment 1 Xavier Claessens 2007-06-14 16:55:28 UTC

Should be fixed in MC 4.23