zeitgeist-daemon crashed with DocNotFoundError in _check_index(): Document 229 not found
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
zeitgeist (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
After starting of QtOctave i get a reproducible Zeitgeist crash.
actions:
1) start QtOctave
observed:
- QtOctave runs
- harddisk is endless active while QTOvtave runs
on systemlog while QtOctave runs:
Sep 3 14:54:29 peter-GA-MA770-UD3 kernel: [ 464.086633] unity-panel-
Sep 3 14:54:30 peter-GA-MA770-UD3 kernel: [ 464.566697] unity-panel-
Sep 3 14:54:30 peter-GA-MA770-UD3 kernel: [ 465.062764] unity-panel-
Sep 3 14:54:31 peter-GA-MA770-UD3 kernel: [ 465.535374] unity-panel-
Sep 3 14:54:32 peter-GA-MA770-UD3 kernel: [ 466.940258] show_signal_msg: 2 callbacks suppressed
Sep 3 14:54:32 peter-GA-MA770-UD3 kernel: [ 466.940262] unity-panel-
Notes:
QtOctave was installed from Software Center
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: zeitgeist-core 0.8.1.1-1
ProcVersionSign
Uname: Linux 3.0.0-9-generic i686
Architecture: i386
Date: Sat Sep 3 14:47:29 2011
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110803.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=en_US.UTF-8
PythonArgs: ['/usr/
SourcePackage: zeitgeist
Title: zeitgeist-daemon crashed with DocNotFoundError in _check_index(): Document 229 not found
Traceback:
Traceback (most recent call last):
File "/usr/share/
hits = self._enquire.
DocNotFoundError: Document 229 not found
UpgradeStatus: Upgraded to oneiric on 2011-08-28 (5 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
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.