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

Bug #1303345 reported by Hari Seldon on 2014-04-06
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
baloo (Ubuntu)
Medium
Unassigned

Bug Description

was trying to restore not stable bumblebee and nvidia drivers on a laptop with optimus

with no success

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 i686
ApportVersion: 2.14.1-0ubuntu1
Architecture: i386
CurrentDesktop: KDE
Date: Sun Apr 6 16:07:09 2014
ExecutablePath: /usr/bin/baloo_file_extractor
InstallationDate: Installed on 2013-06-08 (301 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
ProcCmdline: /usr/bin/baloo_file_extractor 92 91 90
SegvAnalysis:
 Segfault happened at: 0xb724ea31 <_ZNK6Xapian8Database12get_documentEj+33>: mov 0x4(%eax),%edi
 PC (0xb724ea31) ok
 source "0x4(%eax)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: baloo
Stacktrace:
 #0 0xb724ea31 in Xapian::Database::get_document(unsigned int) const () from /usr/lib/sse2/libxapian.so.22
 No symbol table info available.
 #1 0x0804f749 in _start ()
 No symbol table info available.
StacktraceTop:
 Xapian::Database::get_document(unsigned int) const () from /usr/lib/sse2/libxapian.so.22
 _start ()
Title: baloo_file_extractor crashed with SIGSEGV in Xapian::Database::get_document()
UpgradeStatus: Upgraded to trusty on 2014-03-15 (21 days ago)
UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo vboxusers

Hari Seldon (hari-seldon972) wrote :

StacktraceTop:
 Xapian::Database::get_document (this=0x0, did=92) at ../api/omdatabase.cc:439
 Baloo::App::processNextUrl (this=0xbfb3b978) at ../../../../src/file/extractor/app.cpp:129
 QMetaCallEvent::placeMetaCall (this=0x850ebf0, object=0xbfb3b978) at kernel/qobject.cpp:524
 QObject::event (this=0xbfb3b978, e=0x850ebf0) at kernel/qobject.cpp:1194
 QApplicationPrivate::notify_helper (this=0x83d9988, receiver=0xbfb3b978, e=0x850ebf0) at kernel/qapplication.cpp:4567

Changed in baloo (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Harald Sitter (apachelogger) wrote :

Do you still get this crash with 4:4.12.97-0ubuntu2?

information type: Private → Public
Changed in baloo (Ubuntu):
status: New → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for baloo (Ubuntu) because there has been no activity for 60 days.]

Changed in baloo (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers