I just clicked "check" on the update manager and it crashed.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: update-manager 1:0.156.6
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.94-0ubuntu1
Architecture: amd64
Date: Thu Mar 8 19:49:42 2012
ExecutablePath: /usr/bin/update-manager
GsettingsChanges:
com.ubuntu.update-manager first-run false
com.ubuntu.update-manager launch-time 1331235940
com.ubuntu.update-manager window-height 500
com.ubuntu.update-manager window-width 600
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/update-manager
ProcEnviron:
LANGUAGE=en_GB:en
LANG=en_GB.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f0472407986 <_ZNK8pkgCache11VerIterator21TranslatedDescriptionEv+86>: mov 0x14(%rdx),%edx
PC (0x7f0472407986) ok
source "0x14(%rdx)" (0x3f3f242424242438) 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: Upgraded to precise on 2012-02-23 (14 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
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.