Ubuntu
software-center package

software-center crashed with DatabaseError in _database_gen_postlist_iter()

Bug #634128 reported by agbemenu on 2010-09-09

This bug report is a duplicate of: Bug #451555: [MASTER] software-center crashed with DatabaseError (Error reading block *: got end of file). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	software-center (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: software-center

crashed during installation

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: software-center 2.1.17
ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4
Uname: Linux 2.6.35-20-generic i686
Architecture: i386
Date: Thu Sep 9 15:25:53 2010
ExecutablePath: /usr/share/software-center/software-center
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/software-center
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
PythonArgs: ['/usr/bin/software-center']
SourcePackage: software-center
Title: software-center crashed with DatabaseError in _database_gen_postlist_iter()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

agbemenu (asagbemenu) wrote on 2010-09-09:

Dependencies.txt Edit (6.4 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (45.4 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (785 bytes, text/plain; charset="utf-8")
Traceback.txt Edit (1.1 KiB, text/plain; charset="utf-8")

Apport retracing service (apport) on 2010-09-09

tags:

removed: need-duplicate-check

Alex Valavanis (valavanisalex) on 2010-11-27

visibility:

private → public

Revision history for this message

Robert Roth (evfool) wrote on 2011-02-23:

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 #451555, 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. Feel free to continue to report any other bugs you may find.