Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1451669

Summary: Could not send the search request
Product: Red Hat Enterprise Linux 7 Reporter: Martin Krajnak <mkrajnak>
Component: trackerAssignee: Carlos Garnacho <cgarnach>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: high Docs Contact:
Priority: high    
Version: 7.4CC: lmiksik, mcepl, mclasen, mkrajnak, tpelka
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: 1.10.5-4 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-01 22:32:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1449577, 1456511    
Attachments:
Description Flags
error window none

Description Martin Krajnak 2017-05-17 09:22:20 UTC
Created attachment 1279605 [details]
error window

Description of problem:
Error appears in the gtk widget for opening files.

Version-Release number of selected component (if applicable):
tracker-1.10.5-3.el7.x86_64

How reproducible:
always

Two possible reproducers:
Steps to Reproduce:
1.Run gedit
2.Choose Open -> Other Documents ...
3.type any letter after file chooser appears

Steps to Reproduce:
1.Run gnome-disk-utility
2.Choose the menu located in the top of the window
3.Click Restore Disk Image...
4.type any letter after file chooser appears

Actual results:
Could not send the search request
GDBus.Error:org.freedesktop.Tracker1.SparqlError.Internal: 
vtable constructor failed: fts5

Expected results:
WIndow should show the list with query result, no error messages.

Comment 2 Tomas Pelka 2017-05-23 14:40:03 UTC
This is easily reproducible also by nautilus.

Comment 4 Debarshi Ray 2017-06-12 19:17:35 UTC
*** Bug 1436171 has been marked as a duplicate of this bug. ***

Comment 10 Martin Krajnak 2017-06-14 10:13:55 UTC
I've updated the tracker tracker-1.10.5-4.el7.x86_64 and unfortunately I can still reproduce the issue as described in reproducer and also with:
gnome-documents-3.22.2-5.el7.x86_64

Comment 11 Carlos Garnacho 2017-06-14 15:26:30 UTC
It still happens because the Tracker database in your user cache dir was already left in an inconsistent state, Tracker can't easily detect nor recover from this broken state.

Please confirm it does not happen anymore after you do "tracker reset --hard" and "tracker daemon --start".

Comment 12 Martin Krajnak 2017-06-14 15:38:17 UTC
Thank you very much for your instructions, great work! It works now on both my machines I am moving it to verified.

Comment 13 errata-xmlrpc 2017-08-01 22:32:35 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2092