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

[spirosla]

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

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
ApportVersion: 2.14.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: KDE
Date: Sun Apr 6 12:57:46 2014
ExecutablePath: /usr/bin/baloo_file_extractor
InstallationDate: Installed on 2013-11-24 (132 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
ProcCmdline: /usr/bin/baloo_file_extractor 1546 1545 1544 1543 1542 1540 1539 1538 1537 1536 1535 1533 1532 1531 1530 1529 1528 1527 1526 1525 1524 1523 1522 1521 1520 1519 1518 1516 1515 1514 1513 1511 1510 1509 1508 1507 1506 1505 1504 1503
SegvAnalysis:
 Segfault happened at: 0x7fbbc0dabe78 <_ZNK6Xapian8Database12get_documentEj+8>: mov 0x10(%rsi),%rcx
 PC (0x7fbbc0dabe78) 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 0x00007fbbc0dabe78 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: Upgraded to trusty on 2014-01-13 (82 days ago)
UserGroups: adm cdrom debian-tor 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.