tracker-indexer crashed with SIGSEGV in tracker_db_interface_execute_vquery()

Bug #474281 reported by Stefan Leitner
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
tracker (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Binary package hint: tracker

ad 1)
Description: Ubuntu 9.10
Release: 9.10

ad 2)
tracker:
  Installiert: 0.6.95-1ubuntu3
  Kandidat: 0.6.95-1ubuntu3
  Versions-Tabelle:
 *** 0.6.95-1ubuntu3 0
        500 http://ubuntu.uni-klu.ac.at karmic/main Packages
        100 /var/lib/dpkg/status

ad 3)
tracker working

ad 4)
tracker suddenly crashed

ProblemType: Crash
Architecture: i386
Date: Wed Nov 4 16:05:58 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/tracker/tracker-indexer
NonfreeKernelModules: nvidia
Package: tracker 0.6.95-1ubuntu3
ProcCmdline: /usr/lib/tracker/tracker-indexer
ProcEnviron:
 SHELL=/bin/bash
 LANG=de_DE.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x3bec0f: cmpb $0x0,(%eax)
 PC (0x003bec0f) 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: adm admin audio cdrom dialout dip fax floppy fuse libvirtd lpadmin mythtv netdev plugdev powerdev sambashare scanner tape vboxusers video

Revision history for this message
Stefan Leitner (s-o-l) wrote :
visibility: private → public
Revision history for this message
Christopher Meiklejohn (cmeiklejohn) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

Changed in tracker (Ubuntu):
status: New → Incomplete
Revision history for this message
LeeV (leev) wrote :

New install of Karmic, PC turning on about 10mins, just surfing, and tracker crashed unexpectedly...

Revision history for this message
Stefan Leitner (s-o-l) wrote :

* Is this reproducible?

till now this problem didn't appear again.

* If so, what specific steps should we take to recreate this bug?

this happend after upgrading to karmic... like LeeV i was just surfing the web with firefox and reading emails in evolution, the crash was unexpected...

Revision history for this message
LeeV (leev) wrote :

Just happened again. I didn't do anything to start the bug. Just surfing and listening to music.

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.