empathy crashed with SIGSEGV in empathy_dispatcher_chat_with_contact_id()

[Rami Al-Rfou']

Binary package hint: empathy

Empath crashes so often that is hard to figure out what is the trigger.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: empathy 2.31.91.1-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic i686
Architecture: i386
Date: Thu Sep 9 22:57:50 2010
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100823)
ProcCmdline: empathy
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.utf8
SegvAnalysis:
 Segfault happened at: 0x40226d: mov 0xc(%eax),%eax
 PC (0x0040226d) ok
 source "0xc(%eax)" (0x0000000c) 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
 empathy_dispatcher_chat_with_contact_id ()
 empathy_dispatcher_chat_with_contact ()
 ?? ()
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
Title: empathy crashed with SIGSEGV in empathy_dispatcher_chat_with_contact_id()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 empathy_contact_manager_class_intern_init (klass=0x0)
 contact_manager_disconnect_foreach (key=0xa3d4270,
 empathy_individual_view_new (store=0xa373cc0,
 ?? ()
ThreadStacktrace:

[Omer Akram (om26er)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. 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!