aptitude assert failure: *** glibc detected *** aptitude: double free or corruption (!prev): 0x09a805c0 ***

[gokuexe]

Binary package hint: aptitude

Description: Ubuntu lucid (development branch)
Release: 10.04
aptitude:
  Instalados: 0.4.11.11-1ubuntu9
  Candidato: 0.4.11.11-1ubuntu9
  Tabla de versión:
 *** 0.4.11.11-1ubuntu9 0
        500 http://ar.archive.ubuntu.com lucid/main Packages
        500 http://mirrors.kernel.org lucid/main Packages
        100 /var/lib/dpkg/status
I was installing tucan download manager, really i successfully installed tucan, but after that aptitude crashed. tucan works fine
before when I wrote $sudo aptitude install tucan, aptitude asked me for uninstall libiso9660-5{u}, I had accepted all.

ProblemType: Crash
Architecture: i386
AssertionMessage: *** glibc detected *** aptitude: double free or corruption (!prev): 0x09a805c0 ***
Date: Sat Feb 20 06:13:25 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/aptitude
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: aptitude 0.4.11.11-1ubuntu9
ProcAttrCurrent: unconfined (enforce)
ProcCmdline: aptitude install tucan
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=es_AR.utf8
ProcVersionSignature: Ubuntu 2.6.32-13.18-generic
Signal: 6
SourcePackage: aptitude
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libc.so.6
 abort () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
Title: aptitude assert failure: *** glibc detected *** aptitude: double free or corruption (!prev): 0x09a805c0 ***
Uname: Linux 2.6.32-13-generic i686
UserGroups:

[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 #515525, 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.