update-apt-xapian-index crashed with DatabaseError in buildIndex(): Modifications failed (DatabaseOpeningError: Couldn't open base /var/cache/apt-xapian-index/index.3/postlist.tmp to write: No such file or directory), and cannot set consistent table revision numbers: Couldn't reread base A
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| apt-xapian-index (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: apt-xapian-index
Fresh install of Natty Daily iso from 18-Apr-2011.
On first bootup I installed a bunch of packages.
After installing a few packages, I changed the respositories available from software center (enabled partner), I enabled tracking of packages, closed software center and started to install other packages.
After some time (I believe after installing of chromium finished) apport said something crashed.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: apt-xapian-index 0.41ubuntu6
ProcVersionSign
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Tue Apr 19 02:52:14 2011
ExecutablePath: /usr/sbin/
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110418)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/sbin/
ProcEnviron:
PATH=(custom, no user)
SHELL=/bin/sh
PythonArgs: ['/usr/
SourcePackage: apt-xapian-index
Title: update-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
| Lucian Adrian Grijincu (lucian.grijincu) wrote | #1 |
| visibility: | private → public |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| tags: | removed: need-duplicate-check |
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.