tracker-store crashed with SIGSEGV in tracker_db_statement_start_sparql_cursor()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tracker (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Checked for updates via terminal using "sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade", while i had thunderbird running on another workspace. While the crashreport appeared i used the left upper hot corner to search for the steam client which didn't appear because of removing the repository and upgrading to 14.10 yesterday. When typing "st" i saw the apport. Also i updated some python files a short time ahead as i had pithos running which still ran...
ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: tracker 1.0.2-1ubuntu2
ProcVersionSign
Uname: Linux 3.13.0-32-generic x86_64
ApportVersion: 2.14.5-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Mon Aug 4 19:22:15 2014
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2014-04-18 (108 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
ProcCmdline: /usr/lib/
SegvAnalysis:
Segfault happened at: 0x7ffe8ad12714 <tracker_
PC (0x7ffe8ad12714) ok
source "0x28(%rdi)" (0x00000028) not located in a known VMA region (needed readable region)!
destination "%eax" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: tracker
StacktraceTop:
tracker_
?? () from /usr/lib/
tracker_
tracker_
?? ()
Title: tracker-store crashed with SIGSEGV in tracker_
UpgradeStatus: Upgraded to utopic on 2014-08-03 (1 days ago)
UserGroups: adm lpadmin sambashare sudo
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1153285, 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.