empathy crashed with SIGSEGV

[Marat Dyatko]

Binary package hint: empathy

Just do nothing

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: empathy 2.30.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-18.27-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-18-generic i686
Architecture: i386
Date: Tue Mar 30 16:35:57 2010
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcCmdline: empathy
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x80cdf50: mov 0x10(%eax),%eax
 PC (0x080cdf50) ok
 source "0x10(%eax)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 ?? ()
 ?? ()
 ?? () from /usr/lib/libtelepathy-glib.so.0
 ?? () from /usr/lib/libtelepathy-glib.so.0
 ?? () from /usr/lib/libtelepathy-glib.so.0
Title: empathy crashed with SIGSEGV
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 dispatcher_operation_got_contact_cb (factory=0x87cd1a0,
 get_contact_by_handle_cb (connection=0x975e250,
 contacts_context_continue (c=<value optimized out>)
 contacts_context_continue (c=<value optimized out>)
 contacts_context_continue (c=<value optimized out>)

[Omer Akram (om26er)]

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

[Vish (vish)]

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!