tracker-extract crashed with SIGSEGV in MemStream::getChar()

Bug #950765 reported by joshiss
82
This bug affects 18 people
Affects Status Importance Assigned to Milestone
tracker (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

tried searchin some file name and it just crashed

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: tracker-extract 0.12.10-1
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic-pae 3.2.9
Uname: Linux 3.2.0-18-generic-pae i686
ApportVersion: 1.94.1-0ubuntu1
Architecture: i386
Date: Fri Mar 9 11:01:29 2012
ExecutablePath: /usr/lib/tracker/tracker-extract
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: /usr/lib/tracker/tracker-extract
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0xaf624f11 <_ZN9MemStream7getCharEv+17>: movzbl (%ecx),%eax
 PC (0xaf624f11) ok
 source "(%ecx)" (0x030ca9b1) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: tracker
StacktraceTop:
 MemStream::getChar() () from /usr/lib/i386-linux-gnu/libpoppler.so.19
 PDFDoc::getStartXRef() () from /usr/lib/i386-linux-gnu/libpoppler.so.19
 PDFDoc::setup(GooString*, GooString*) () from /usr/lib/i386-linux-gnu/libpoppler.so.19
 PDFDoc::PDFDoc(BaseStream*, GooString*, GooString*, void*) () from /usr/lib/i386-linux-gnu/libpoppler.so.19
 poppler_document_new_from_data () from /usr/lib/i386-linux-gnu/libpoppler-glib.so.8
Title: tracker-extract crashed with SIGSEGV in MemStream::getChar()
UpgradeStatus: Upgraded to precise on 2012-03-09 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
joshiss (joshiss) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 MemStream::getChar() () from /tmp/tmpVoybwu/usr/lib/i386-linux-gnu/libpoppler.so.19
 PDFDoc::getStartXRef() () from /tmp/tmpVoybwu/usr/lib/i386-linux-gnu/libpoppler.so.19
 PDFDoc::setup(GooString*, GooString*) () from /tmp/tmpVoybwu/usr/lib/i386-linux-gnu/libpoppler.so.19
 PDFDoc::PDFDoc(BaseStream*, GooString*, GooString*, void*) () from /tmp/tmpVoybwu/usr/lib/i386-linux-gnu/libpoppler.so.19
 poppler_document_new_from_data () from /tmp/tmpVoybwu/usr/lib/i386-linux-gnu/libpoppler-glib.so.8

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in tracker (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Jeremy Bícha (jbicha)
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in tracker (Ubuntu):
status: New → Confirmed
Revision history for this message
iMac (imac-netstatz) wrote :

Just happened a short while after reboot in my case.

Revision history for this message
Obulapathi (obulpathi) wrote :

System reported that Ubuntu detected an internal error and advised me try rebooting if the error persists.

Revision history for this message
Mengxuan Xia (xiamx) wrote :

This bug is also present in amd64 arch.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.