zeitgeist-daemon crashed with DatabaseError in _check_index(): Error reading block 26: Bad file descriptor

[José Antonio]

zeitgeist had a high cpu usage (the system monitor indicated was oscillating between 95 to 120%), force closing it with the system monitor caused this crash warning to appear.

jose@JARR-Laptop:~$ lsb_release -rd
Description: Ubuntu oneiric (development branch)
Release: 11.10

jose@JARR-Laptop:~$ apt-cache policy zeitgeist
zeitgeist:
  Installed: 0.8.1.1-1
  Candidate: 0.8.1.1-1
  Version table:
 *** 0.8.1.1-1 0
        500 http://archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: zeitgeist-core 0.8.1.1-1
ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
NonfreeKernelModules: nvidia wl
Architecture: amd64
Date: Sat Sep 3 01:54:00 2011
ExecutablePath: /usr/bin/zeitgeist-daemon
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/zeitgeist-daemon
PythonArgs: ['/usr/bin/zeitgeist-daemon']
SourcePackage: zeitgeist
Title: zeitgeist-daemon crashed with DatabaseError in _check_index(): Error reading block 26: Bad file descriptor
Traceback:
 Traceback (most recent call last):
   File "/usr/share/zeitgeist/_zeitgeist/engine/extensions/fts.py", line 283, in _check_index
     hits = self._enquire.get_mset (0, 1)
 DatabaseError: Error reading block 26: Bad file descriptor
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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