update-apt-xapian-index crashed with DatabaseCorruptError in buildIndex(): Failed to unlink /var/cache/apt-xapian-index/index.3/postlist.baseB: No such file or directory
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apt-xapian-index (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: apt-xapian-index
This happened on a very recently installed Natty i386 system, running apt-xapian-index 0.41ubuntu5. I don't know what triggered this bug. I had updated the system (which only involved updates to a few packages since I had installed from the daily live image), and was proceeding to install and configure VMware Tools (which I doubt is causally related to this problem).
I doubt they're relevant, but in case they are, I'll attach /var/log/dpkg.log as well as the Terminal log from the VMware Tools installation and configuration (up to the point when Apport informed me of this crash).
As is typical of crashes in apt-xapian-index, if Apport had not informed me of the crash, I would have no idea that any crash had occurred.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: apt-xapian-index 0.41ubuntu5
ProcVersionSign
Uname: Linux 2.6.38-5-generic i686
Architecture: i386
Date: Fri Mar 4 10:50:06 2011
ExecutablePath: /usr/sbin/
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110304)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/sbin/
ProcEnviron:
LANGUAGE=en_US:en
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/
SourcePackage: apt-xapian-index
Title: update-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
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 #631215, 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.