aptd crashed with SIGSEGV in debListParser::LoadReleaseInfo()

[Jason Young]

reboot after upgrade running 11.10 beta 1

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: aptdaemon 0.43+bzr697
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Sun Sep 25 13:04:27 2011
DesktopFile: /usr/share/aptdaemon/aptdaemon.desktop
ExecutablePath: /usr/sbin/aptd
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/sbin/aptd
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x7f90bd175686 <_ZN13debListParser15LoadReleaseInfoERN8pkgCache15PkgFileIteratorER6FileFdSs+630>: rex
 PC (0x7f90bd175686) ok
 SP (0x7fffefb15cf0) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: aptdaemon
StacktraceTop:
 debListParser::LoadReleaseInfo(pkgCache::PkgFileIterator&, FileFd&, std::string) () from /usr/lib/libapt-pkg.so.4.11
 debTranslationsIndex::Exists() const () from /usr/lib/libapt-pkg.so.4.11
 ?? ()
 ?? ()
 ?? ()
SysLog:
 Sep 26 19:45:33 jason-Aspire-7552 AptDaemon: INFO: Initializing daemon
 Sep 26 19:45:33 jason-Aspire-7552 AptDaemon: INFO: UpgradeSystem() was called with safe mode: 1
 Sep 26 19:45:33 jason-Aspire-7552 AptDaemon.Trans: INFO: Simulate was called
 Sep 26 19:45:33 jason-Aspire-7552 AptDaemon.Worker: INFO: Simulating trans: /org/debian/apt/transaction/6021630184014a25b278a70611326c1b
 Sep 26 19:45:37 jason-Aspire-7552 AptDaemon.Worker: INFO: Upgrade system with safe mode: 1
Title: aptd crashed with SIGSEGV in debListParser::LoadReleaseInfo()
UpgradeStatus: Upgraded to oneiric on 2011-09-23 (3 days ago)
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 #860057, 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.