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

[Joel Stanley]

Fresh reboot into gnome-shell and apport triggered on login.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: tracker-miner-fs 1.0.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-13.19-generic 3.16.1
Uname: Linux 3.16.0-13-generic x86_64
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Sun Sep 7 19:18:38 2014
ExecutablePath: /usr/lib/tracker/tracker-miner-fs
ProcCmdline: /usr/lib/tracker/tracker-miner-fs
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_AU.UTF-8
 LANGUAGE=en_AU:en
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x7f43b7347f2f <g_type_check_instance_is_a+63>: testb $0x4,0x16(%rax)
 PC (0x7f43b7347f2f) ok
 source "$0x4" ok
 destination "0x16(%rax)" (0x5320545245534e5e) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: tracker
StacktraceTop:
 g_type_check_instance_is_a (type_instance=type_instance@entry=0x14ec0e0, iface_type=iface_type@entry=20438304) at /build/buildd/glib2.0-2.41.3/./gobject/gtype.c:3969
 g_file_get_uri (file=0x14ec0e0) at /build/buildd/glib2.0-2.41.3/./gio/gfile.c:546
 ?? () from /usr/lib/x86_64-linux-gnu/libtracker-miner-1.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libtracker-miner-1.0.so.0
 g_cclosure_marshal_VOID__BOOLEANv (closure=<optimised out>, return_value=<optimised out>, instance=<optimised out>, args=<optimised out>, marshal_data=<optimised out>, n_params=<optimised out>, param_types=0x144a960) at /build/buildd/glib2.0-2.41.3/./gobject/gmarshal.c:188
Title: tracker-miner-fs crashed with SIGSEGV in g_type_check_instance_is_a()
UpgradeStatus: Upgraded to utopic on 2014-09-02 (5 days ago)
UserGroups: adm cdrom dialout dip docker kvm libvirtd 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 #1337220, 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.