software-center crashed with KeyError in __getitem__(): "The cache has no package named 'xfsprogs'"

Bug #764860 reported by Zephyr
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
software-center (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: software-center

appears when I have tried to install cairo-clock without internet connection

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: software-center 3.1.26.4
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CheckboxSubmission: 52411fe8b29896970a09af9dcb81231f
CheckboxSystem: 0531969bcfd4f03af7405c98dc94a948
Date: Sun Apr 17 20:00:56 2011
ExecutablePath: /usr/share/software-center/software-center
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110329.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/software-center gparted/Редактор\ разделов\ диска\ GNOME
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=ru_RU:en
 LANG=ru_RU.UTF-8
PythonArgs: ['/usr/bin/software-center', 'gparted/\xd0\xa0\xd0\xb5\xd0\xb4\xd0\xb0\xd0\xba\xd1\x82\xd0\xbe\xd1\x80 \xd1\x80\xd0\xb0\xd0\xb7\xd0\xb4\xd0\xb5\xd0\xbb\xd0\xbe\xd0\xb2 \xd0\xb4\xd0\xb8\xd1\x81\xd0\xba\xd0\xb0 GNOME']
SourcePackage: software-center
Title: software-center crashed with KeyError in __getitem__(): "The cache has no package named 'xfsprogs'"
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin nopasswdlogin plugdev sambashare

Revision history for this message
Zephyr (pasha-pivo) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #729225, 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.

tags: removed: need-duplicate-check
visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.