software-center crashed with DocNotFoundError in __init__(): Document 953 not found

Bug #722177 reported by Terry-friedmann
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

running ubuntu 11.04 development branch upgraded from 10.10. Ran a search for 'moon' followed by a search for 'silver' in software-center 3.1.19 which instead of producing the resulting search, prompted this error. Application did not crash, just produced this error. I was able to re-run the query without restarting the application.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: software-center 3.1.19
ProcVersionSignature: Ubuntu 2.6.38-4.31-generic 2.6.38-rc5
Uname: Linux 2.6.38-4-generic i686
Architecture: i386
Date: Sun Feb 20 10:00:16 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/share/software-center/software-center
InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release i386 (20101007)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/software-center
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 LC_MESSAGES=en_US.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/software-center']
SourcePackage: software-center
Title: software-center crashed with DocNotFoundError in __init__(): Document 953 not found
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Terry-friedmann (terry-friedmann) wrote :
Revision history for this message
Terry-friedmann (terry-friedmann) wrote :

additional note, this was discovered on netbook hardware (atom processor, 1.5GB RAM, 100GB hard drive) running over an 802.11g wireless network, so may be a simple latency issue whether due to the network or the speed of the processing hardware.

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 #703558, 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.