update-software-center-channels crashed with KeyError in __getitem__(): "The cache has no package named 'libogre-1.7.3'"

[u-foka]

popped up after closing software center

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: software-center 5.1.12
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic-pae 3.2.9
Uname: Linux 3.2.0-18-generic-pae i686
NonfreeKernelModules: wl
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
Date: Sun Mar 11 18:59:29 2012
ExecutablePath: /usr/share/software-center/update-software-center-channels
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120210)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/software-center/update-software-center-channels
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/share/software-center/update-software-center-channels']
SourcePackage: software-center
Title: update-software-center-channels crashed with KeyError in __getitem__(): "The cache has no package named 'libogre-1.7.3'"
UpgradeStatus: Upgraded to precise on 2012-02-13 (26 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Robert Roth (evfool)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

[Gary Lasker (gary-lasker)]

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 863594, 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. Please continue to report any other bugs you may find.