update-manager crashed with SIGSEGV in pkgCache::VerIterator::TranslatedDescription()

[zerocoolre]

ubuntu 12.04

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: update-manager 1:0.156.8
ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11
Uname: Linux 3.2.0-19-generic x86_64
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Tue Mar 20 12:36:05 2012
ExecutablePath: /usr/bin/update-manager
GsettingsChanges:
 com.ubuntu.update-manager first-run false
 com.ubuntu.update-manager launch-time 1332184311
 com.ubuntu.update-manager window-height 600
 com.ubuntu.update-manager window-width 609
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/update-manager --no-focus-on-map
SegvAnalysis:
 Segfault happened at: 0x7f768626a986 <_ZNK8pkgCache11VerIterator21TranslatedDescriptionEv+86>: mov 0x14(%rdx),%edx
 PC (0x7f768626a986) ok
 source "0x14(%rdx)" (0x3f3f3f3f3f3f3f53) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: update-manager
StacktraceTop:
 pkgCache::VerIterator::TranslatedDescription() const () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12
 ?? () from /usr/lib/python2.7/dist-packages/apt_pkg.so
 ?? ()
 _PyObject_GenericGetAttrWithDict ()
 _PyAptObject_getattro(_object*, _object*) () from /usr/lib/python2.7/dist-packages/apt_pkg.so
Title: update-manager crashed with SIGSEGV in pkgCache::VerIterator::TranslatedDescription()
UpgradeStatus: Upgraded to precise on 2012-03-13 (7 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

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