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

Bug #771781 reported by L Franko
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

it happens when i log in

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 x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Mon Apr 25 08:31:47 2011
ExecutablePath: /usr/sbin/update-apt-xapian-index
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/sbin/update-apt-xapian-index --batch-mode --force
ProcEnviron:

PythonArgs: ['/usr/sbin/update-apt-xapian-index', '--batch-mode', '--force']
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: Upgraded to natty on 2011-04-20 (7 days ago)
UserGroups:

Revision history for this message
L Franko (lori-ramwools) 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 #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.

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.