This happened in the background, so I'm not exactly sure what caused it. But I was shuffling quite a few e books around on the hard drive and adding them to the Calibre Library. Probably related to that. Default configuration for Tracker, except I'd added three more directories to follow in $HOME.
On a fully up-to-date Ubuntu-GNOME Raring Ringtail with gnome-shell 3.8 from the gnome3 and gnome3-staging PPAs.
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: tracker-miner-fs 0.15.4-0ubuntu1~raring1 [origin: LP-PPA-gnome3-team-gnome3]
ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
Uname: Linux 3.8.0-16-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
Date: Mon Apr 8 01:40:31 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/tracker/tracker-miner-fs
InstallationDate: Installed on 2013-04-04 (3 days ago)
InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
MarkForUpload: True
ProcCmdline: /usr/lib/tracker/tracker-miner-fs
SegvAnalysis:
Segfault happened at: 0x7f0b185725ac <g_type_check_instance_is_a+60>: testb $0x4,0x16(%rdi)
PC (0x7f0b185725ac) ok
source "$0x4" ok
destination "0x16(%rdi)" (0x00004732) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: tracker
StacktraceTop:
g_type_check_instance_is_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
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
Title: tracker-miner-fs crashed with SIGSEGV in g_type_check_instance_is_a()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
Happens to me everytime I boot now.