Ubuntu
update-notifier package

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

Bug #542934 reported by messajunior
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
update-notifier (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: update-notifier

Aplicativo travou

ProblemType: Crash
Architecture: i386
Date: Sat Mar 20 16:47:42 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/lib/update-notifier/apt_check.py
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
InterpreterPath: /usr/bin/python2.6
Package: update-notifier-common 0.98
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/lib/update-notifier/apt-check
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
SegvAnalysis:
 Segfault happened at: 0x14625e <_ZN8pkgCache7FindPkgERKSs+110>: movzbl (%edx),%eax
 PC (0x0014625e) ok
 source "(%edx)" (0x25e9012e) 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::ListParser::NewDepends(pkgCache::VerIterator, std::string const&, std::string const&, unsigned int, unsigned int) ()
 debListParser::ParseDepends(pkgCache::VerIterator, char const*, unsigned int) () from /usr/lib/libapt-pkg-libc6.10-6.so.4.8
 debListParser::NewVersion(pkgCache::VerIterator) ()
Title: apt_check.py crashed with SIGSEGV in pkgCache::FindPkg()
Uname: Linux 2.6.32-16-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #521128, 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.

visibility: private → public
tags: removed: need-i386-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.