tracker-indexer crashed with SIGSEGV in tracker_db_interface_execute_vquery()

[Anand Kumria]

Binary package hint: tracker

Binary package hint: wv

1)

eve[~]% lsb_release -rd
Description: Ubuntu 9.10
Release: 9.10

2)

eve[~]% apt-cache policy tracker
tracker:
  Installed: 0.6.95-1ubuntu1
  Candidate: 0.6.95-1ubuntu1
  Version table:
 *** 0.6.95-1ubuntu1 0
        500 http://uk.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

3)

No crash dialog to appear

4)

I activated tracker indexing and I started getting these dialog popping up.

I am assuming that tracker is calling an external command, which is failing.

ProblemType: Crash
Architecture: i386
Date: Thu Oct 22 17:14:11 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=/usr/bin/zsh
 PATH=(custom, no user)
 LANGUAGE=C
 LANG=C
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x3ecc0f: cmpb $0x0,(%eax)
 PC (0x003ecc0f) 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-14-generic i686
UserGroups: admin audio camera cdrom dialout dip disk fax floppy fuse libvirtd lpadmin netdev plugdev powerdev sambashare scanner tape video

[Apport retracing service (apport)]

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.