update-apt-xapian-index crashed with DatabaseError in buildIndex(): Modifications failed (DatabaseCorruptError: Failed to unlink /var/cache/apt-xapian-index/index.3/spelling.baseA: Aucun fichier ou dossier de ce type), and cannot set consistent table revision numbers: Couldn't reread base B

[JPh. Bocquenet]

Binary package hint: apt-xapian-index

Description: Ubuntu natty (development branch)
Release: 11.04
apt-xapian-index:
  Installé : 0.41ubuntu5
  Candidat : 0.41ubuntu5
 Table de version :
 *** 0.41ubuntu5 0
        500 http://fr.archive.ubuntu.com/ubuntu/ natty/main i386 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: apt-xapian-index 0.41ubuntu5
ProcVersionSignature: Ubuntu 2.6.38-3.30-generic 2.6.38-rc4
Uname: Linux 2.6.38-3-generic i686
Architecture: i386
Date: Tue Feb 15 09:59:55 2011
ExecutablePath: /usr/sbin/update-apt-xapian-index
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110214)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/sbin/update-apt-xapian-index --update -q
ProcEnviron:
 LANGUAGE=fr_FR.UTF-8:en
 PATH=(custom, no user)
 LANG=fr_FR.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: Aucun fichier ou dossier de ce type), and cannot set consistent table revision numbers: Couldn't reread base B
UserGroups:

[Apport retracing service (apport)]

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.