empathy crashed with SIGSEGV in g_slice_free1()

[Gabriel Bauman]

Binary package hint: empathy

Not sure what happened to trigger this.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: empathy 2.30.0-0ubuntu4
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic i686
Architecture: i386
Date: Wed Apr 7 23:01:03 2010
ExecutablePath: /usr/bin/empathy
ProcCmdline: /usr/bin/empathy -h
ProcEnviron:
 LANG=en_CA.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x89bb53e: mov (%eax),%ecx
 PC (0x089bb53e) ok
 source "(%eax)" (0x00000005) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 ?? () from /lib/libglib-2.0.so.0
 g_slice_free1 () from /lib/libglib-2.0.so.0
 g_slist_free_1 () from /lib/libglib-2.0.so.0
 g_slist_remove () from /lib/libglib-2.0.so.0
 ?? () from /usr/lib/libdbus-glib-1.so.2
Title: empathy crashed with SIGSEGV in g_slice_free1()
UserGroups: adm admin cdrom dialout dip fax floppy fuse kvm lpadmin plugdev sambashare tape vboxusers video

[Apport retracing service (apport)]

StacktraceTop:
 ?? () from /lib/libglib-2.0.so.0
 g_slice_free1 () from /lib/libglib-2.0.so.0
 g_slist_free_1 () from /lib/libglib-2.0.so.0
 g_slist_remove () from /lib/libglib-2.0.so.0
 dbus_g_proxy_manager_unregister (manager=0x9e2fe00,

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Gabriel Bauman (gabrielbauman)]

I'll try, but I've only seen this once. It's unlikely that I'll get the requested log, so I guess this bug will probably expire.

[Sebastien Bacher (seb128)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.