update-apt-xapian-index crashed with DatabaseCorruptError in buildIndex(): Failed to unlink /var/cache/apt-xapian-index/index.4/postlist.baseA: No such file or directory

Bug #750313 reported by Andrew Painter
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

Had Synaptic Package Manager open along with the Update Manager. Changed the default update server to main from canada as one of the updates wouldn't download then the crash happened.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: apt-xapian-index 0.41ubuntu5
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
Architecture: amd64
Date: Mon Apr 4 10:12:00 2011
ExecutablePath: /usr/sbin/update-apt-xapian-index
InterpreterPath: /usr/bin/python2.7
ProcCmdline: /usr/bin/python /usr/sbin/update-apt-xapian-index --batch-mode --force --update
ProcEnviron:

PythonArgs: ['/usr/sbin/update-apt-xapian-index', '--batch-mode', '--force', '--update']
SourcePackage: apt-xapian-index
Title: update-apt-xapian-index crashed with DatabaseCorruptError in buildIndex(): Failed to unlink /var/cache/apt-xapian-index/index.4/postlist.baseA: No such file or directory
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Andrew Painter (andrewpainter) 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 #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.

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.