zeitgeist-daemon crashed with DocNotFoundError in _check_index(): Document 16 not found

Bug #839975 reported by Doug McMahon
This bug report is a duplicate of:  Bug #722762: zeitgeist-daemon using ~100% of CPU. Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Zeitgeist Extensions
New
Undecided
Unassigned
zeitgeist (Ubuntu)
New
Undecided
Unassigned

Bug Description

This is occurring upon login after the upgrade of zeitgeist-extension-fts to 0.0.10-0ubuntu1
Before doing the libglib2.0-0 upgrades to 2.29.18-0ubuntu3 zeitgeist-daemon would not crash but would use close to 100% cpu
After the glib upgrade the daemon crashes upon login

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 i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Fri Sep 2 19:26:15 2011
ExecutablePath: /usr/bin/zeitgeist-daemon
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110831)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/zeitgeist-daemon
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
PythonArgs: ['/usr/bin/zeitgeist-daemon']
SourcePackage: zeitgeist
Title: zeitgeist-daemon crashed with DocNotFoundError in _check_index(): Document 16 not found
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)
 DocNotFoundError: Document 16 not found
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare

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 #839739, 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.