update-manager crashed with SIGSEGV in pkgCache::VerIterator::TranslatedDescription()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-manager (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I had simply told the Update Manager to check for new updates, manually. After it finished checking, it seemed to sloooowly scroll through each update item. After a while it crashed completely. I was able to rerun Update Manager and start a partial upgrade just fine. If this can be replicated, then I hope this helps. If not, simply close it.
can provide more info if needed, not sure what would be useful at the moment...
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: update-manager 1:0.156.6
ProcVersionSign
Uname: Linux 3.2.0-17-generic x86_64
ApportVersion: 1.93-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Fri Mar 9 15:12:06 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/
GsettingsChanges:
com.ubuntu.
com.ubuntu.
com.ubuntu.
com.ubuntu.
com.ubuntu.
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
SegvAnalysis:
Segfault happened at: 0x7fec0e837986 <_ZNK8pkgCache1
PC (0x7fec0e837986) ok
source "0x14(%rdx)" (0x243f3f3f3f3f
destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: update-manager
StacktraceTop:
pkgCache:
?? () from /usr/lib/
?? ()
?? ()
_PyAptObject_
Title: update-manager crashed with SIGSEGV in pkgCache:
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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.