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 3.5.7.4
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
ProcEnviron:
LANGUAGE=en_US:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
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
StacktraceTop:
tracker_db_statement_start_sparql_cursor () from /usr/lib/tracker-0.14/libtracker-data.so.0
?? () from /usr/lib/tracker-0.14/libtracker-data.so.0
tracker_sparql_query_execute_cursor () from /usr/lib/tracker-0.14/libtracker-data.so.0
tracker_data_query_sparql_cursor () from /usr/lib/tracker-0.14/libtracker-data.so.0
?? ()
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
Status changed to 'Confirmed' because the bug affects multiple users.