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
i used the mouse on activities to show all open windows. firefox, system settings with browsing details and software update manager. i used to try to change the size of the details window while having all windows on the screen. on the left the launcher bar - on the right the workspaces. while trying to change the size of the system details window i moved it over the others. moved over firefox with hitting space bar after trying some other shortcuts, like + and - ; control with + and - with scrolling the mouse wheel. directly when hitting space bar the error occurred.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: tracker 0.16.2-1ubuntu1
ProcVersionSign
Uname: Linux 3.11.0-11-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Mon Oct 7 22:41:51 2013
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2013-08-16 (52 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
ProcCmdline: /usr/lib/
SegvAnalysis:
Segfault happened at: 0x7f99d747f764 <tracker_
PC (0x7f99d747f764) 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_
?? () from /usr/lib/
tracker_
tracker_
?? ()
Title: tracker-store crashed with SIGSEGV in tracker_
UpgradeStatus: Upgraded to saucy on 2013-09-01 (36 days ago)
UserGroups: adm cdrom dip lpadmin plugdev 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.