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

Bug #1056355 reported by Mathieu Marquer
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
update-notifier (Ubuntu)
Expired
Medium
Unassigned

Bug Description

While updating packages

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: update-notifier-common 0.122
ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
Uname: Linux 3.5.0-15-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
Date: Tue Sep 25 19:33:28 2012
ExecutablePath: /usr/lib/update-notifier/apt_check.py
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/lib/update-notifier/apt-check
ProcEnviron:
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f857d4f2794 <_ZN8pkgCache5ReMapERKb+116>: cmp %rcx,(%rdi)
 PC (0x7f857d4f2794) ok
 source "%rcx" ok
 destination "(%rdi)" (0xffffffffffffffff) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: update-notifier
StacktraceTop:
 pkgCache::ReMap(bool const&) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12
 pkgCache::pkgCache(MMap*, bool) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12
 ?? () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12
 pkgCacheGenerator::MakeStatusCache(pkgSourceList&, OpProgress*, MMap**, bool) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12
 pkgCacheFile::BuildCaches(OpProgress*, bool) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12
Title: apt_check.py crashed with SIGSEGV in pkgCache::ReMap()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Mathieu Marquer (slasher-fun) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 pkgCache::ReMap (this=this@entry=0x7fff9ae9a900, Errorchecks=Errorchecks@entry=@0x7fff9ae9a7ee: true) at pkgcache.cc:152
 pkgCache::pkgCache (this=0x7fff9ae9a900, Map=<optimized out>, DoMap=<optimized out>) at pkgcache.cc:122
 CheckValidity (CacheFile=..., List=..., Start=..., End=..., OutMap=OutMap@entry=0x0) at pkgcachegen.cc:1061
 pkgCacheGenerator::MakeStatusCache (List=..., Progress=0x7fff9ae9ae40, OutMap=0x29fd000, AllowMem=<optimized out>) at pkgcachegen.cc:1337
 pkgCacheFile::BuildCaches (this=this@entry=0x29fcff0, Progress=Progress@entry=0x7fff9ae9ae40, WithLock=false) at cachefile.cc:83

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in update-notifier (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in update-notifier (Ubuntu):
status: New → Confirmed
Revision history for this message
Paul White (paulw2u) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.

Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.

I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time.

Changed in update-notifier (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for update-notifier (Ubuntu) because there has been no activity for 60 days.]

Changed in update-notifier (Ubuntu):
status: Incomplete → Expired
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.