update-apt-xapian-index crashed with DatabaseError in buildIndex(): Modifications failed (DatabaseCorruptError: Failed to unlink /var/cache/apt-xapian-index/index.3/spelling.baseA: No such file or directory), and cannot set consistent table revision numbers: Couldn't reread base B

Bug #730732 reported by Brian Kennedy
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apt-xapian-index (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: apt-xapian-index

This is running in a VirtualBox OSE instance on Ubuntu 10.10's stock version of VB OSE. I selected the virtualbox-guest-x11 package for isntallation and its dependencies, clicked apply, and boom.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: apt-xapian-index 0.41ubuntu5
ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
Uname: Linux 2.6.38-5-generic x86_64
Architecture: amd64
Date: Mon Mar 7 11:52:37 2011
ExecutablePath: /usr/sbin/update-apt-xapian-index
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/sbin/update-apt-xapian-index --update -q
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/sbin/update-apt-xapian-index', '--update', '-q']
SourcePackage: apt-xapian-index
Title: update-apt-xapian-index crashed with DatabaseError in buildIndex(): Modifications failed (DatabaseCorruptError: Failed to unlink /var/cache/apt-xapian-index/index.3/spelling.baseA: No such file or directory), and cannot set consistent table revision numbers: Couldn't reread base B
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Brian Kennedy (ekspiulo) 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 #633003, 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.