tracker-store crashed with SIGSEGV in tracker_db_statement_start_sparql_cursor()

Bug #1153285 reported by caspar luc on 2013-03-10
This bug affects 11 people
Affects Status Importance Assigned to Milestone
tracker (Ubuntu)

Bug Description

appeared after running bleachbit in normal user mode.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: tracker 0.14.5-1ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-24.37-generic
Uname: Linux 3.5.0-24-generic x86_64
ApportVersion: 2.9.1-0ubuntu1
Architecture: amd64
Date: Mon Mar 11 00:10:57 2013
ExecutablePath: /usr/lib/tracker/tracker-store
InstallationDate: Installed on 2012-01-29 (405 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MarkForUpload: True
ProcCmdline: /usr/lib/tracker/tracker-store
 PATH=(custom, no user)
 Segfault happened at: 0x7f8c775bf2a4 <tracker_db_statement_start_sparql_cursor+4>: mov 0x28(%rdi),%r10d
 PC (0x7f8c775bf2a4) ok
 source "0x28(%rdi)" (0x00000028) not located in a known VMA region (needed readable region)!
 destination "%r10d" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: tracker
 tracker_db_statement_start_sparql_cursor () from /usr/lib/tracker-0.14/
 ?? () from /usr/lib/tracker-0.14/
 tracker_sparql_query_execute_cursor () from /usr/lib/tracker-0.14/
 tracker_data_query_sparql_cursor () from /usr/lib/tracker-0.14/
 ?? ()
Title: tracker-store crashed with SIGSEGV in tracker_db_statement_start_sparql_cursor()
UpgradeStatus: Upgraded to raring on 2013-03-02 (7 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

caspar luc (luc-caspar) wrote :
Changed in tracker (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Launchpad Janitor (janitor) wrote :

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

Changed in tracker (Ubuntu):
status: New → Confirmed
tags: added: saucy
tags: added: bugpattern-needed
tags: added: trusty
tags: added: utopic
Tim Lunn (darkxst) on 2014-08-08
information type: Private → Public
To post a comment you must log in.