empathy crashed with SIGSEGV in g_source_destroy()

[dolfdiop]

Binary package hint: empathy

ubuntu lucid

ProblemType: Crash
Architecture: amd64
Date: Fri Feb 26 22:06:29 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
Package: empathy 2.29.91-1ubuntu1
ProcCmdline: empathy
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=fr_FR.utf8
ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
SegvAnalysis:
 Segfault happened at: 0x7f45e168bbc5 <g_source_destroy+5>: mov 0x20(%rdi),%rsi
 PC (0x7f45e168bbc5) ok
 source "0x20(%rdi)" (0xaaaaaaaaaaaaaaca) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 g_source_destroy () from /lib/libglib-2.0.so.0
 ?? () from /usr/lib/libsoup-2.4.so.1
 ?? () from /usr/lib/libsoup-2.4.so.1
 soup_socket_connect_async ()
 ?? () from /usr/lib/libsoup-2.4.so.1
Title: empathy crashed with SIGSEGV in g_source_destroy()
Uname: Linux 2.6.32-14-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 g_source_destroy () from /lib/libglib-2.0.so.0
 disconnect_internal (priv=0x2a325c0)
 socket_connect_internal (sock=<value optimized out>)
 soup_socket_connect_async (sock=0x2a325a0,
 run_queue (sa=<value optimized out>)

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