telepathy-haze crashed with SIGSEGV in strncmp()

[Hebert]

Binary package hint: telepathy-haze

After today's update I can't connect to yahoo using empathy.

empathy:
  Instalado: 2.23.6-0ubuntu4
  Candidato: 2.23.6-0ubuntu4
  Tabela de versão:
 *** 2.23.6-0ubuntu4 0
        500 http://br.archive.ubuntu.com intrepid/universe Packages
        100 /var/lib/dpkg/status

telepathy-haze:
  Instalado: 0.2.0-1
  Candidato: 0.2.0-1
  Tabela de versão:
 *** 0.2.0-1 0
        500 http://br.archive.ubuntu.com intrepid/universe Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/telepathy/telepathy-haze
Package: telepathy-haze 0.2.0-1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/lib/telepathy/telepathy-haze
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=pt_BR.UTF-8
Signal: 11
SourcePackage: telepathy-haze
StacktraceTop:
 strncmp () from /lib/libc.so.6
 ?? () from /usr/lib/purple-2/libyahoo.so
 ?? ()
 g_main_context_dispatch ()
 ?? () from /usr/lib/libglib-2.0.so.0
Title: telepathy-haze crashed with SIGSEGV in strncmp()
Uname: Linux 2.6.26-5-generic x86_64
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:strncmp () from /lib/libc.so.6
yahoo_pending (data=0x1f20630, source=10, cond=PURPLE_INPUT_READ)
purple_glib_io_invoke (source=<value optimized out>,
IA__g_main_context_dispatch (context=0x1eaf440)
g_main_context_iterate (context=0x1eaf440, block=1, dispatch=1,

[Sebastien Bacher (seb128)]

the crash is a libpurple one

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Could you try to reproduce the same with Ubuntu 8.10 or 9.04? Thanks in advance.

[Pedro Villavicencio (pedro)]

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!.