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

[Rafael A. de Almeida]

Binary package hint: update-notifier

Estava atualizando o sistema através do terminal. Um tempo após ter terminado a atualização recebi uma mensagem informando que ouve um erro no update-notifier.

Description: Ubuntu 9.10
Release: 9.10

update-notifier:
  Instalado: 0.90
  Candidato: 0.90
  Tabela de versão:
 *** 0.90 0
        500 http://br.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: i386
Date: Mon Oct 26 05:47:28 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/update-notifier/apt_check.py
InterpreterPath: /usr/bin/python2.6
Package: update-notifier-common 0.90
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/lib/update-notifier/apt-check
ProcEnviron:
 LANGUAGE=pt_BR.UTF-8
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0xcd6924 <_ZN8pkgCache7FindPkgERKSs+132>: movzbl (%edi),%eax
 PC (0x00cd6924) ok
 source "(%edi)" (0xea2ac000) not located in a known VMA region (needed readable region)!
 destination "%eax" 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
Title: apt_check.py crashed with SIGSEGV in pkgCache::FindPkg()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare tty

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