I see this bug occasionally at random intervals. I'm running a virtualbox instance right now, but I also see it on my laptop (both currently running ubuntu 14.10, I believe).
I don't see it on any regular basis, but I do use gnome3 instead of unity, and perhaps that might be an issue? ppa:gnome3-team/gnome3 is the only big ppa I use.
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: tracker-miner-fs 0.16.4-0ubuntu1~trusty4 [origin: LP-PPA-gnome3-team-gnome3]
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Jun 4 11:52:46 2014
ExecutablePath: /usr/lib/tracker/tracker-miner-fs
InstallationDate: Installed on 2014-06-04 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcCmdline: /usr/lib/tracker/tracker-miner-fs
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7ff82c1a7f8e <g_file_get_child+30>: cmp %rax,(%rdx)
PC (0x7ff82c1a7f8e) ok
source "%rax" ok
destination "(%rdx)" (0x00001e93) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: tracker
StacktraceTop:
g_file_get_child () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
?? () from /usr/lib/libtracker-miner-0.16.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: tracker-miner-fs crashed with SIGSEGV in g_file_get_child()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
StacktraceTop:
?? ()
?? ()
?? ()
?? ()
?? ()