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

Bug #446722 reported by Emilio
260
This bug affects 58 people
Affects Status Importance Assigned to Milestone
update-notifier (Ubuntu)
Confirmed
Undecided
Benjamin

Bug Description

Binary package hint: update-notifier

This happened twice in my systems, in both cases I was running synaptic, and it was installing packages. A red icon appeared on the tray, with an error that said something I don't remember, and then said this might be caused by broken dependencies - but the first error wasn't related with dependencies in any way.

ProblemType: Crash
Architecture: amd64
Date: Thu Oct 8 16:45:04 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/update-notifier/apt_check.py
InterpreterPath: /usr/bin/python2.6
Package: update-notifier-common 0.88
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/lib/update-notifier/apt-check
ProcEnviron:
 PATH=(custom, user)
 LANG=es_AR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-12.41-generic
SegvAnalysis:
 Segfault happened at: 0x7fa35b340e41 <_ZN8pkgCache7FindPkgERKSs+145>: movzbl 0x0(%rbp),%edx
 PC (0x7fa35b340e41) ok
 source "0x0(%rbp)" (0x7fa3bf8c3600) 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
 ?? () 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-12-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

Revision history for this message
Emilio (turl) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? ()
?? ()
?? ()
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in update-notifier (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

lsb-release: installed version 4.0-0ubuntu4, latest version: 4.0-0ubuntu5
python2.6: installed version 2.6.3-0ubuntu2, latest version: 2.6.4~rc1-0ubuntu1
python2.6-minimal: installed version 2.6.3-0ubuntu2, latest version: 2.6.4~rc1-0ubuntu1
update-notifier-common: installed version 0.88, latest version: 0.89

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
Changed in update-notifier (Ubuntu):
status: Invalid → Confirmed
Changed in update-notifier (Ubuntu):
assignee: nobody → Benjamin (mastermindbird)
Revision history for this message
benditoelqueviene (quasar1970) wrote :

The same error here, but the system didn't say anything about dependencies. It was about apt_check.py. I was searching new security updates and tried to confirm them when it happened.

Revision history for this message
Christopher (soft-kristal) wrote :

Also affecting Lucid periodically. My system crashed while running this morning's update. On reboot, this message appeared and even apt-get update/upgrade in a terminal behaved oddly. I ended up updating via Synaptics Package Manager.

It may be related to bug 261523 - update-apt-xapian-index crashed with SystemError in open().

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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