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

[Arno Waschk]

happens regularly

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: baloo 4:4.12.97-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-17.37-lowlatency 3.13.6
Uname: Linux 3.13.0-17-lowlatency x86_64
ApportVersion: 2.14.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: KDE
Date: Sat Apr 5 21:28:12 2014
ExecutablePath: /usr/bin/baloo_file_extractor
InstallationDate: Installed on 2014-03-13 (23 days ago)
InstallationMedia: Ubuntu-Studio 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
ProcCmdline: /usr/bin/baloo_file_extractor 2263 2262 2261 2260 2259 2258 2257 2256 2255 2254 2253 2252 2251 2249 2248 2247 2246 2245 2244 2243 2242 2241 2240 2239 2238 2237 2236 2235 2234 2233 2231 2230 2229 2228 2227 2226 2225 2224 2223 2221
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f7b85acfe78 <_ZNK6Xapian8Database12get_documentEj+8>: mov 0x10(%rsi),%rcx
 PC (0x7f7b85acfe78) 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 0x00007f7b85acfe78 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-03-13 (23 days ago)
UserGroups: adm audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare scanner sudo tape video

[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.