empathy crashed with SIGSEGV

[Hebert]

Binary package hint: empathy

lsb_release -rd
Description: Ubuntu lucid (development branch)
Release: 10.04

$ apt-cache policy empathy
empathy:
  Installed: 2.29.6-0ubuntu2
  Candidate: 2.29.6-0ubuntu2
  Version table:
 *** 2.29.6-0ubuntu2 0
        500 http://archive.ubuntu.com lucid/main Packages
        100 /var/lib/dpkg/status

I was trying to initiate a videochat with a friend when empathy crasehed.

ProblemType: Crash
Architecture: amd64
Date: Thu Feb 4 17:17:16 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/empathy
InstallationMedia: Error: [Errno 13] Permissão negada: '/var/log/installer/media-info'
Package: empathy 2.29.6-0ubuntu2
ProcCmdline: empathy
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=pt_BR.utf8
 LANG=pt_BR.utf8
ProcVersionSignature: Ubuntu 2.6.32-12.16-generic
SegvAnalysis:
 Segfault happened at: 0x473585: mov 0x10(%rax),%rax
 PC (0x00473585) ok
 source "0x10(%rax)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: empathy crashed with SIGSEGV
Uname: Linux 2.6.32-12-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 empathy_video_widget_get_element (widget=<value optimized out>)
 ?? ()
 ?? ()
 ?? ()
 ?? ()

[Apport retracing service (apport)]

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libebook1.2-9: installed version 2.28.2-1ubuntu2, latest version: 2.28.2-1ubuntu3
libedataserver1.2-11: installed version 2.28.2-1ubuntu2, latest version: 2.28.2-1ubuntu3
libcamel1.2-14: installed version 2.28.2-1ubuntu2, latest version: 2.28.2-1ubuntu3

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!