aptitude-curses crashed with SIGABRT in __assert_fail_base()

[Anders Kaseorg]

aptitude-curses crashed with SIGABRT in __assert_fail_base()

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: aptitude 0.6.11-1ubuntu3
ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
Uname: Linux 3.19.0-9-generic x86_64
NonfreeKernelModules: openafs
ApportVersion: 2.16.2-0ubuntu4
Architecture: amd64
Date: Mon Mar 23 04:11:16 2015
ExecutablePath: /usr/bin/aptitude-curses
InstallationDate: Installed on 2014-08-22 (212 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140730)
ProcCmdline: aptitude full-upgrade
Signal: 6
SourcePackage: aptitude
StacktraceTop:
 __assert_fail_base (fmt=0x7fc27cff9028 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7fc27f7cfae9 "pthread_mutex_lock(&m_)==0", file=file@entry=0x7fc27f7cfc88 "/usr/include/boost/flyweight/detail/recursive_lw_mutex.hpp", line=line@entry=72, function=function@entry=0x7fc27f801e80 "boost::flyweights::detail::recursive_lightweight_mutex::scoped_lock::scoped_lock(boost::flyweights::detail::recursive_lightweight_mutex&)") at assert.c:92
 __GI___assert_fail (assertion=0x7fc27f7cfae9 "pthread_mutex_lock(&m_)==0", file=0x7fc27f7cfc88 "/usr/include/boost/flyweight/detail/recursive_lw_mutex.hpp", line=72, function=0x7fc27f801e80 "boost::flyweights::detail::recursive_lightweight_mutex::scoped_lock::scoped_lock(boost::flyweights::detail::recursive_lightweight_mutex&)") at assert.c:101
 ?? ()
 ?? ()
 ?? ()
Title: aptitude-curses crashed with SIGABRT in __assert_fail_base()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: sbuild

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1348921, 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.