apt-get crashed with SIGSEGV in pkgCache::DepIterator::IsSatisfied()

Bug #1296495 reported by Chris
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apt (Ubuntu)
New
Undecided
Unassigned

Bug Description

Updated the system to the newest 14.04 daily using update-manager gui. After restart, crash occured immediately after entering login credentials, before the desktop had loaded.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: apt 0.9.15.4ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6
Uname: Linux 3.13.0-17-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
Date: Tue Mar 18 07:35:02 2014
ExecutablePath: /usr/bin/apt-get
InstallationDate: Installed on 2014-02-21 (31 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140218)
ProcCmdline: apt-get check -qq
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 SHELL=/bin/sh
SegvAnalysis:
 Segfault happened at: 0x7fe3cdd68c29 <_ZNK8pkgCache11DepIterator11IsSatisfiedERKNS_11VerIteratorE+41>: mov (%rax),%edi
 PC (0x7fe3cdd68c29) ok
 source "(%rax)" (0x7fe3ce4b3690) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: apt
StacktraceTop:
 pkgCache::DepIterator::IsSatisfied(pkgCache::VerIterator const&) const () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12
 pkgDepCache::CheckDep(pkgCache::DepIterator, int, pkgCache::PkgIterator&) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12
 pkgDepCache::DependencyState(pkgCache::DepIterator&) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12
 pkgDepCache::Update(OpProgress*) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12
 pkgDepCache::Init(OpProgress*) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12
Title: apt-get crashed with SIGSEGV in pkgCache::DepIterator::IsSatisfied()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Chris (ganglere) wrote :
information type: Private → Public
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 this software better. This particular crash has already been reported and is a duplicate of bug #1215703, 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.

tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

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