aptd crashed with SIGSEGV in pkgDepCache::Update()

[Tony Mugan]

Just got this in a Unity 2D session in Oneiric.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: aptdaemon 0.43+bzr697
Uname: Linux 3.0.4-030004-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Sun Sep 25 18:20:42 2011
DesktopFile: /usr/share/aptdaemon/aptdaemon.desktop
ExecutablePath: /usr/sbin/aptd
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/sbin/aptd
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x7fd351928f03 <_ZN11pkgDepCache6UpdateEP10OpProgress+451>: mov 0x14(%rax),%r14d
 PC (0x7fd351928f03) ok
 source "0x14(%rax)" (0x7fd34e26d5e8) not located in a known VMA region (needed readable region)!
 destination "%r14d" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: aptdaemon
StacktraceTop:
 pkgDepCache::Update(OpProgress*) () from /usr/lib/libapt-pkg.so.4.11
 pkgDepCache::Init(OpProgress*) () from /usr/lib/libapt-pkg.so.4.11
 pkgCacheFile::BuildDepCache(OpProgress*) () from /usr/lib/libapt-pkg.so.4.11
 pkgCacheFile::Open(OpProgress*, bool) () from /usr/lib/libapt-pkg.so.4.11
 ?? () from /usr/lib/python2.7/dist-packages/apt_pkg.so
Title: aptd crashed with SIGSEGV in pkgDepCache::Update()
UpgradeStatus: Upgraded to oneiric on 2011-09-20 (4 days ago)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 pkgDepCache::Update (this=0x2363e10, Prog=0x7fff3a95bff0) at depcache.cc:678
 pkgDepCache::Init (this=0x2363e10, Prog=0x7fff3a95bff0) at depcache.cc:158
 pkgCacheFile::BuildDepCache (this=0x212c410, Progress=0x7fff3a95bff0) at cachefile.cc:140
 pkgCacheFile::Open (this=0x212c410, Progress=0x7fff3a95bff0, WithLock=<optimized out>) at cachefile.cc:155
 Open (Progress=..., this=0x212c410, WithLock=<optimized out>) at /usr/include/apt-pkg/cachefile.h:62

[Julian Andres Klode (juliank)]

Either a bug in the connection between aptdaemon's progress handler and python-apt, or the cache file is broken. The first option seems unlikely, as it does not turn up in the stacktrace.

[Julian Andres Klode (juliank)]

Closing as invalid, there's nothing we can do here. It might just be a broken cache file.