After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 762577 - Searching in file chooser sometimes triggers tracker error
Searching in file chooser sometimes triggers tracker error
Status: RESOLVED DUPLICATE of bug 762226
Product: tracker
Classification: Core
Component: FTS
unspecified
Other Linux
: Normal normal
: ---
Assigned To: tracker-general
tracker-general
Depends on:
Blocks:
 
 
Reported: 2016-02-24 04:02 UTC by Michael Catanzaro
Modified: 2016-02-26 15:00 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Michael Catanzaro 2016-02-24 04:02:27 UTC 
Sometimes when searching in the file chooser, I get an error dialog:

"""
Could not send the search request

GDBus.Error:org.freedesktop.Tracker1.SparqlError.Internal: unknown tokenizer: TrackerTokenizer
"""

My journal contains only one relevant line:

Feb 23 21:55:59 victory-road org.freedesktop.Tracker1[9685]: (tracker-store:10032): Tracker-WARNING **: Could not create FTS insert statement: unknown tokenizer: TrackerTokenizer


It's somehow tied to the directory I execute the search from. I'm currently able to reproduce it reliably by searching for anything inside my WebKit/Source directory (including subdirectories), but not in other directories on my system.
Comment 1 Michael Catanzaro 2016-02-24 04:04:04 UTC 
GTK+ 3.18.7
Comment 2 Michael Catanzaro 2016-02-26 01:04:58 UTC 
Anything I could do to help debug this? It's really annoying....
Comment 3 Matthias Clasen 2016-02-26 01:06:20 UTC 
I would suggest that this is a tracker issue.
Comment 4 Carlos Garnacho 2016-02-26 02:04:37 UTC 
It is.

*** This bug has been marked as a duplicate of bug 762226 ***
Comment 5 Michael Catanzaro 2016-02-26 14:55:28 UTC 
Are you sure it's a dup of bug #762226? The initial database was created a month or two ago, last time I reported a tracker bug with the file chooser and you had me delete my previous database, definitely before 3.11.0 was released.
Comment 6 Carlos Garnacho 2016-02-26 15:00:33 UTC 
Yes, this is a thing we do at runtime, a tokenizer must be registered on TrackerDBInterface/TrackerSparqlConnection startup so it's correctly looked up and used in FTS queries. The "newly created database" info there is bogus.