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

[NeoSting]

when checking for news updates and before it ends. But the update-manager is still here.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: update-manager 1:0.156.7
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94-0ubuntu2
Architecture: amd64
Date: Tue Mar 6 22:31:14 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/update-manager
GsettingsChanges:
 com.ubuntu.update-manager first-run false
 com.ubuntu.update-manager launch-time 1331069484
 com.ubuntu.update-manager window-height 500
 com.ubuntu.update-manager window-width 600
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/update-manager --no-focus-on-map
ProcEnviron:
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7ff5edd30986 <_ZNK8pkgCache11VerIterator21TranslatedDescriptionEv+86>: mov 0x14(%rdx),%edx
 PC (0x7ff5edd30986) ok
 source "0x14(%rdx)" (0x100000013) 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
 ?? ()
 ?? ()
 _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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[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.