speech-dispatcher assert failure: *** glibc detected *** /usr/bin/speech-dispatcher: double free or corruption (!prev): 0x0000000000816780 ***

[Olisemeka Omo]

Binary package hint: speech-dispatcher

Just did an update again..
Error came up during Gnome bootup

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: speech-dispatcher 0.7.1-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.38-6.34-generic 2.6.38-rc7
Uname: Linux 2.6.38-6-generic x86_64
Architecture: amd64
AssertionMessage: *** glibc detected *** /usr/bin/speech-dispatcher: double free or corruption (!prev): 0x0000000000816780 ***
Date: Wed Mar 16 19:29:02 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/speech-dispatcher
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
ProcCmdline: /usr/bin/speech-dispatcher --spawn --communication-method unix_socket --socket-path /home/User Name/.speech-dispatcher/speechd.sock --port 7560
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: speech-dispatcher
StacktraceTop:
 raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
 abort () at abort.c:92
 __libc_message (do_abort=2, fmt=0x7f2e0c4f43e0 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
 malloc_printerr (av=<value optimized out>, p=0x816770) at malloc.c:6283
 _int_free (av=<value optimized out>, p=0x816770) at malloc.c:4795
Title: speech-dispatcher assert failure: *** glibc detected *** /usr/bin/speech-dispatcher: double free or corruption (!prev): 0x0000000000816780 ***
UpgradeStatus: Upgraded to natty on 2011-03-04 (13 days ago)
UserGroups: adm admin cdrom dialout lpadmin mythtv netdev plugdev sambashare

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #725765, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.