tracker-miner-fs crashed with SIGSEGV in tracker_file_system_unset_property()

[magowiz]

it happened once I logged in , I don't know what caused it.

$ lsb_release -rd
Description: Ubuntu 14.04.1 LTS
Release: 14.04

$ apt-cache policy tracker
tracker:
  Installed: 0.16.4-0ubuntu0.1
  Candidate: 0.16.4-0ubuntu0.1
  Version table:
 *** 0.16.4-0ubuntu0.1 0
        500 http://it.archive.ubuntu.com/ubuntu/ trusty-updates/universe amd64 Packages
        100 /var/lib/dpkg/status
     0.16.2-1ubuntu4 0
        500 http://it.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: tracker-miner-fs 0.16.4-0ubuntu0.1 [modified: usr/lib/tracker/tracker-miner-fs]
ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
Uname: Linux 3.13.0-34-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Aug 25 11:33:34 2014
ExecutablePath: /usr/lib/tracker/tracker-miner-fs
ProcCmdline: /usr/lib/tracker/tracker-miner-fs
SegvAnalysis:
 Segfault happened at: 0x7f0167b2a39c <__strncmp_ssse3+44>: movlpd (%rdi),%xmm1
 PC (0x7f0167b2a39c) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%xmm1" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: tracker
StacktraceTop:
 ?? () from /usr/lib/libtracker-miner-0.16.so.0
 ?? () from /usr/lib/libtracker-miner-0.16.so.0
 tracker_file_system_unset_property () from /usr/lib/libtracker-miner-0.16.so.0
 ?? () from /usr/lib/libtracker-miner-0.16.so.0
 ?? () from /usr/lib/libtracker-miner-0.16.so.0
Title: tracker-miner-fs crashed with SIGSEGV in tracker_file_system_unset_property()
UpgradeStatus: Upgraded to trusty on 2014-04-19 (127 days ago)
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 #976281, 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.