tracker-store crashed with SIGSEGV in tracker_db_statement_start_sparql_cursor()

[Removed by request]

Crashed happened when launching System Testing

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: tracker 0.16.2-1ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu May 1 14:30:13 2014
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/tracker/tracker-store
InstallationDate: Installed on 2014-05-01 (0 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
ProcCmdline: /usr/lib/tracker/tracker-store
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f0fd7953714 <tracker_db_statement_start_sparql_cursor+4>: mov 0x28(%rdi),%eax
 PC (0x7f0fd7953714) ok
 source "0x28(%rdi)" (0x00000028) 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 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.