tracker-store crashed with SIGSEGV in tracker_db_statement_start_sparql_cursor()

[Cefn]

No idea what this is. I'm running saucy with backports and proposed, so probably this needs to be looked into before some package streams into the main repos.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: tracker 0.16.1-1ubuntu2
ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
Uname: Linux 3.11.0-9-generic i686
ApportVersion: 2.12.5-0ubuntu1
Architecture: i386
Date: Sat Sep 28 11:51:18 2013
ExecutablePath: /usr/lib/tracker/tracker-store
InstallationDate: Installed on 2013-08-15 (43 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha i386 (20130626)
MarkForUpload: True
ProcCmdline: /usr/lib/tracker/tracker-store
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb77030da <tracker_db_statement_start_sparql_cursor+42>: mov 0x14(%edx),%eax
 PC (0xb77030da) ok
 source "0x14(%edx)" (0x00000014) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: tracker
StacktraceTop:
 tracker_db_statement_start_sparql_cursor () from /usr/lib/tracker-0.16/libtracker-data.so.0
 ?? () from /usr/lib/tracker-0.16/libtracker-data.so.0
 tracker_sparql_query_execute_cursor () from /usr/lib/tracker-0.16/libtracker-data.so.0
 tracker_data_query_sparql_cursor () from /usr/lib/tracker-0.16/libtracker-data.so.0
 ?? ()
Title: tracker-store crashed with SIGSEGV in tracker_db_statement_start_sparql_cursor()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1153285, 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.