empathy-accounts crashed with SIGSEGV in tp_proxy_get_object_path()

[John Markh]

Binary package hint: empathy

Crashes when deleting an VoIP account through "Messaging and VoIP Accounts" (System -> Preferences).

ProblemType: Crash
Architecture: i386
Date: Sat Feb 27 09:53:21 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/empathy-accounts
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100113)
Package: empathy 2.29.91-1ubuntu2
ProcCmdline: empathy-accounts
ProcEnviron:
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
SegvAnalysis:
 Segfault happened at: 0x269516 <tp_proxy_get_object_path+38>: mov 0x18(%eax),%eax
 PC (0x00269516) ok
 source "0x18(%eax)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 tp_proxy_get_object_path ()
 ?? ()
 ?? ()
 ?? ()
 g_cclosure_marshal_VOID__OBJECT ()
Title: empathy-accounts crashed with SIGSEGV in tp_proxy_get_object_path()
Uname: Linux 2.6.32-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1356): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (gnome-power-manager:1344): Gtk-CRITICAL **: gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed
 (bluetooth-applet:1352): Gtk-CRITICAL **: gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed

[Apport retracing service (apport)]

StacktraceTop:
 tp_proxy_get_object_path (self=0x0) at proxy.c:1157
 empathy_account_settings_has_account (settings=0x99e1008,
 accounts_dialog_get_account_iter (
 accounts_dialog_account_removed_cb (manager=0x9952860,
 g_cclosure_marshal_VOID__OBJECT ()

[Omer Akram (om26er)]

thanks for the bug report. is this still an issue?

[Omer Akram (om26er)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. If this is still an issue, Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[Omer Akram (om26er)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!