zeitgeist-fts crashed with SIGSEGV in getint2()

[cliff tinker]

not sure what but the only program running is backuup(restore)

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: zeitgeist-core 0.8.99~alpha3-1
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.93-0ubuntu2
Architecture: amd64
Date: Sun Feb 26 10:27:05 2012
ExecutablePath: /usr/lib/zeitgeist/zeitgeist-fts
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120201.2)
ProcCmdline: /usr/lib/zeitgeist/zeitgeist-fts
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f15466c859d <_ZN10ChertTable13find_in_blockEPKh3Keybi+13>: movzbl 0x9(%rdi),%r13d
 PC (0x7f15466c859d) ok
 source "0x9(%rdi)" (0x00000009) not located in a known VMA region (needed readable region)!
 destination "%r13d" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: zeitgeist
StacktraceTop:
 ChertTable::find_in_block(unsigned char const*, Key, bool, int) () from /usr/lib/libxapian.so.22
 ChertTable::find(Cursor*) const () from /usr/lib/libxapian.so.22
 ChertTable::delete_kt() () from /usr/lib/libxapian.so.22
 ChertTable::del(std::string const&) () from /usr/lib/libxapian.so.22
 ?? () from /usr/lib/libxapian.so.22
Title: zeitgeist-fts crashed with SIGSEGV in ChertTable::find_in_block()
UpgradeStatus: Upgraded to precise on 2012-02-26 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 getint2 (c=9, p=<optimized out>) at ../common/unaligned.h:50
 ChertTable::find_in_block (p=0x0, key=..., leaf=false, c=-1) at ../backends/chert/chert_table.cc:463
 ChertTable::find (this=0x18caa38, C_=0x18caae8) at ../backends/chert/chert_table.cc:497
 ChertTable::delete_kt (this=0x18caa38) at ../backends/chert/chert_table.cc:960
 ChertTable::del (this=0x18caa38, key=<optimized out>) at ../backends/chert/chert_table.cc:1159

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.