GNOME Bugzilla – Bug 785876
No search results returned: Could not get search results, GDBus.Error:org.freedesktop.Tracker1.SparqlError.Internal: no such tokenizer: TrackerTokenizer
Last modified: 2017-08-22 10:34:51 UTC
Whenever I try to search for something, I will get Could not get search results, GDBus.Error:org.freedesktop.Tracker1.SparqlError.Internal: no such tokenizer: TrackerTokenizer and zero results In the meantime, I tried rm -rf .cache/tracker to have everything reindexed, but that didn't change a thing (there are tens of thousands of documents in the index but still it hever returns search results. I am on current arch linux
I guess for now this can be closed again. a tracker reset -r did the trick.
Actually, the latter worked only on Debian Stretch with tracker 0.10.1, on Arch with Tracker 0.12, the situation is still unchanged. Did another tracker reset -r, but when running tracker search [some search term] I still get zero results and the above error message.
sorry, this is the last change for now: Reopening.
(In reply to Johannes Rohr from comment #2) > Actually, the latter worked only on Debian Stretch with tracker 0.10.1, on > Arch with Tracker 0.12. I assume you mean 1.10/1.12? > the situation is still unchanged. Did another > tracker reset -r, but when running tracker search [some search term] I still > get zero results and the above error message. Resetting the database won't help. Tokenizers need to be registered at runtime for every underlying database connection, so this is definitely a runtime error. The good news is that this bug was found and fixed in master (bug #784926, although the symptoms were different there). I'm pushing a backported fix to 1.12. In the mean time, you can work around it by running tracker search with the TRACKER_SPARQL_BACKEND=bus envvar set.
The following fix has been pushed: 0bd32cd libtracker-data: Do not reuse TrackerDBInterface used for DB checks
Created attachment 357047 [details] [review] libtracker-data: Do not reuse TrackerDBInterface used for DB checks It is just too soon to let it initialize like the others, just drop it and let the TrackerDBManager create proper ones on demand. (Cherry picked from commit 5c61827 on master)
> > In the mean time, you can work around it by running tracker search with the > TRACKER_SPARQL_BACKEND=bus envvar set. Does not work here unfortunately, therefore reopening: TRACKER_SPARQL_BACKEND=bus tracker search linux Suchergebnisse konnten nicht angefordert werden, GDBus.Error:org.freedesktop.Tracker1.SparqlError.Internal: no such tokenizer: TrackerTokenizer
Please only reopen this bug if you have tested the *patch* that has been pushed and found it doesn't fix the problem for you. REOPENED only applies if the fix was ineffective/incomplete, or the bug was reintroduced in other ways. The workaround just lowers the chances for this to happen, if it didn't work for you, such is life. You can also use nautilus or tracker-needle as the tracker search interface, where there's again lower chances for this to happen just by how queries are performed asynchronously.
*** This bug has been marked as a duplicate of bug 785883 ***