baloo_file_extractor crashed with SIGSEGV in Xapian::Database::get_document()

[Zach Leigh]

One of several baloo crashes that occurred simultaneously.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: baloo 4:4.12.97-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
Uname: Linux 3.13.0-23-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu1
Architecture: amd64
CurrentDesktop: KDE
Date: Sun Apr 6 10:31:10 2014
ExecutablePath: /usr/bin/baloo_file_extractor
InstallationDate: Installed on 2014-03-10 (26 days ago)
InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140227)
ProcCmdline: /usr/bin/baloo_file_extractor 58 53 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 22 21 20 19 18 16 11 10 9 8 7 6 5 4
SegvAnalysis:
 Segfault happened at: 0x7f894dd81e78 <_ZNK6Xapian8Database12get_documentEj+8>: mov 0x10(%rsi),%rcx
 PC (0x7f894dd81e78) ok
 source "0x10(%rsi)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%rcx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: baloo
Stacktrace:
 #0 0x00007f894dd81e78 in Xapian::Database::get_document(unsigned int) const () from /usr/lib/libxapian.so.22
 No symbol table info available.
 #1 0x0000000000408f2e in _start ()
 No symbol table info available.
StacktraceTop:
 Xapian::Database::get_document(unsigned int) const () from /usr/lib/libxapian.so.22
 _start ()
Title: baloo_file_extractor crashed with SIGSEGV in Xapian::Database::get_document()
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 #1301742, 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.