Comment 3 for bug 731854

@Martin: Are you sure you have the zeitgeist-fts-extension installed? And if you do, I guess the index is somehow corrupted... You can try to kill zeitgeist-daemon and look at ~/.local/share/zeitgeist/fts.index. Mine looks like:

$ ls -lh ~/.local/share/zeitgeist/fts.index/
total 2,2M
-rw-r--r-- 1 kamstrup kamstrup 0 2011-03-11 08:38 flintlock
-rw-r--r-- 1 kamstrup kamstrup 28 2011-03-08 14:32 iamchert
-rw-r--r-- 1 kamstrup kamstrup 29 2011-03-11 10:58 position.baseA
-rw-r--r-- 1 kamstrup kamstrup 29 2011-03-11 10:58 position.baseB
-rw-r--r-- 1 kamstrup kamstrup 704K 2011-03-11 10:58 position.DB
-rw-r--r-- 1 kamstrup kamstrup 25 2011-03-11 10:58 postlist.baseA
-rw-r--r-- 1 kamstrup kamstrup 24 2011-03-11 10:58 postlist.baseB
-rw-r--r-- 1 kamstrup kamstrup 520K 2011-03-11 10:58 postlist.DB
-rw-r--r-- 1 kamstrup kamstrup 18 2011-03-11 10:58 record.baseA
-rw-r--r-- 1 kamstrup kamstrup 18 2011-03-11 10:58 record.baseB
-rw-r--r-- 1 kamstrup kamstrup 40K 2011-03-11 10:58 record.DB
-rw-r--r-- 1 kamstrup kamstrup 32 2011-03-11 10:58 termlist.baseA
-rw-r--r-- 1 kamstrup kamstrup 32 2011-03-11 10:58 termlist.baseB
-rw-r--r-- 1 kamstrup kamstrup 944K 2011-03-11 10:58 termlist.DB

While ZG is not running you try try and just delete ~/.local/share/zeitgeist/fts.index - it will be rebuild when ZG starts up next time. Maybe this fixes you issues?

You can also try and poke at the Zeitgeist logs in ~/.cache/zeitgeist to see if anything is suspicious...