apt_check.py crashed with SIGSEGV in pkgProblemResolver::MakeScores()

[Benjamin Geese]

Happened after restarting ubuntu. I did apt-get dist-upgrade before that.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: update-notifier-common 0.118.1ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-11.19-generic 3.2.1
Uname: Linux 3.2.0-11-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Fri Jan 27 17:21:13 2012
ExecutablePath: /usr/lib/update-notifier/apt_check.py
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/lib/update-notifier/apt-check
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fa9df79c4da <_ZN18pkgProblemResolver10MakeScoresEv+1658>: cmp %rdi,0x18(%rax)
 PC (0x7fa9df79c4da) ok
 source "%rdi" ok
 destination "0x18(%rax)" (0x04ab7b38) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: update-notifier
StacktraceTop:
 pkgProblemResolver::MakeScores() () from /usr/lib/libapt-pkg.so.4.11
 pkgProblemResolver::ResolveInternal(bool) () from /usr/lib/libapt-pkg.so.4.11
 pkgProblemResolver::Resolve(bool) () from /usr/lib/libapt-pkg.so.4.11
 pkgDistUpgrade(pkgDepCache&) () from /usr/lib/libapt-pkg.so.4.11
 ?? () from /usr/lib/python2.7/dist-packages/apt_pkg.so
Title: apt_check.py crashed with SIGSEGV in pkgProblemResolver::MakeScores()
UpgradeStatus: Upgraded to precise on 2011-12-11 (46 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Robert Roth (evfool)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #453968, so it 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. Feel free to continue to report any other bugs you may find.