apt_check.py crashed with SIGSEGV in pkgCache::FindPkg()

[Jari J. Lehtinen]

Binary package hint: update-notifier

Apport reported this error on 10.04 (standard 32-bit Gnome version)
I did not notice any harm yet, before this indication of software failure.
The Appotś error indicator comes to the panel on every start of the desktop-environment
I hope Apport has collected all nescassery information.

ProblemType: Crash
Architecture: i386
Date: Mon Jan 18 19:57:55 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/lib/update-notifier/apt_check.py
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100113)
InterpreterPath: /usr/bin/python2.6
Package: update-notifier-common 0.92
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/lib/update-notifier/apt-check
ProcEnviron:
 LANG=fi_FI.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-10.14-generic
SegvAnalysis:
 Segfault happened at: 0xc779e0 <_ZN8pkgCache7FindPkgERKSs+96>: mov (%esi),%edx
 PC (0x00c779e0) ok
 source "(%esi)" (0xbb691000) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: update-notifier
StacktraceTop:
 pkgCache::FindPkg(std::string const&) ()
 pkgCacheGenerator::NewPackage(pkgCache::PkgIterator&, std::string const&) () from /usr/lib/libapt-pkg-libc6.10-6.so.4.8
 pkgCacheGenerator::MergeList(pkgCacheGenerator::ListParser&, pkgCache::VerIterator*) () from /usr/lib/libapt-pkg-libc6.10-6.so.4.8
 debStatusIndex::Merge(pkgCacheGenerator&, OpProgress&) const
 ?? () from /usr/lib/libapt-pkg-libc6.10-6.so.4.8
Tags: lucid
Title: apt_check.py crashed with SIGSEGV in pkgCache::FindPkg()
Uname: Linux 2.6.32-10-generic i686
UserGroups: adm admin cdrom dialout lpadmin 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 #467875, 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.