tracker-indexer crashed with SIGSEGV in tracker_db_interface_execute_vquery()

Bug #438154 reported by Prunus dulcis
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tracker (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: tracker

Ubuntu karmic

The tracker indexer crashed with the summary crash report message and now has stopped indexing files.

ProblemType: Crash
Architecture: i386
Date: Mon Sep 28 15:35:36 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/tracker/tracker-indexer
Package: tracker 0.6.95-1ubuntu1
ProcCmdline: /usr/lib/tracker/tracker-indexer
ProcEnviron:
 SHELL=/bin/bash
 LANG=de_DE.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
SegvAnalysis:
 Segfault happened at: 0x527c0f: cmpb $0x0,(%eax)
 PC (0x00527c0f) ok
 source "$0x0" ok
 destination "(%eax)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: tracker
StacktraceTop:
 ?? () from /usr/lib/libsqlite3.so.0
 ?? () from /usr/lib/libsqlite3.so.0
 ?? () from /usr/lib/libsqlite3.so.0
 ?? () from /usr/lib/tracker/libtracker-db.so.0
 tracker_db_interface_execute_vquery ()
Title: tracker-indexer crashed with SIGSEGV in tracker_db_interface_execute_vquery()
Uname: Linux 2.6.31-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Prunus dulcis (prunus-dulcis) wrote :

After a restart, first tracker gave the info it had finished indexing all files withing 1 and a half minutes, when I checked the statistics, it had zero in all entries and now it started indexing all over again. Something really seems to be broken here.
As a note, sometimes I think, the indexing stopped due to too low disk space. I moved files to make more space. It told me it was working again afterwards but the statistics did not go up.

visibility: private → public
Revision history for this message
Prunus dulcis (prunus-dulcis) wrote :

Now after another restart, tracker gave a short note about an invalid index and started all over again. With all the bugs it has right now, sadly for me it is completely unusable, since it does not completely build the index and the index gets corrupted after a normal restart of the notebook, so it has to build it all fresh again :-(

Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #410485, 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.

tags: removed: need-i386-retrace
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.