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

[marioohoa]

Binary package hint: apt-xapian-index

bhbh

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: apt-xapian-index 0.41ubuntu6
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Sun Apr 24 00:40:10 2011
ExecutablePath: /usr/sbin/update-apt-xapian-index
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110413)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/sbin/update-apt-xapian-index --quiet
ProcEnviron:
 PATH=(custom, no user)
 SHELL=/bin/sh
PythonArgs: ['/usr/sbin/update-apt-xapian-index', '--quiet']
SourcePackage: apt-xapian-index
Title: update-apt-xapian-index crashed with DatabaseError in buildIndex(): Modifications failed (DatabaseOpeningError: Couldn't open base /var/cache/apt-xapian-index/index.3/spelling.baseA to write: No such file or directory), and cannot set consistent table revision numbers: Couldn't reread base A
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Jamie Strandboge (jdstrand)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

[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 #629112, 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.