How configure gnome quick search locations properly?

Hi there,

I configured my search locations after figuring out that I could quick search files from the gnome “overview”, which is accessible via the SUPER key.

I added the path /media/Daten/100-Persönlich in Other locations. See this screenshot:

I added an example file in this location:

If I press SUPER and type Johnny, I expect the file to show up in the search results, but it doesn’t:


(Keine Ergebnisse :== No results)

How can I solve this?

Best regards

It takes some time until the files has been added to the index. In fact the quick search uses the tracker3 index.

Maybe test this on the terminal:

tracker3 search Johnny

I am not sure, but the global search when typing SUPER is restricted to $HOME only, but when searching in nautilus it is restricted to the current working dir recursively.

systemctl --user edit tracker-miner-fs-3.service

and add there:

[Service]
Environment=TRACKER_DEBUG=config,statistics,miner-fs-events

then run:

systemctl --user restart tracker-miner-fs-3.service && journalctl --user --unit=tracker-miner-fs-3.service --unit=tracker-extract-3.service -f

Then you should see some more details about what it is doing in the background.

It does find the occurrences of the file. So, the index is alright, I guess.

$ tracker3 status
Currently indexed: 55382 files, 5430 folders
Remaining space on database partition: 38.1?GB (26.88%)
All data miners are idle, indexing complete
52 recorded failures

The log looks good to me (deleted some lines, which stated that it found and processed other directories).

Mai 20 16:17:27 ${HOSTNAME} tracker-miner-f[96328]:   Adding:'/usr/local/share/applications'
Mai 20 16:17:27 ${HOSTNAME} tracker-miner-f[96328]:   Adding:'/usr/share/applications'
Mai 20 16:17:27 ${HOSTNAME} tracker-miner-f[96328]:   Adding:'/home/${USER}/.local/share/applications'
Mai 20 16:17:27 ${HOSTNAME} tracker-miner-f[96328]: Not setting disk space, configuration is set to -1 (disabled)
Mai 20 16:17:27 ${HOSTNAME} tracker-miner-f[96328]: Current and previous locales match: 'de_DE.UTF-8'
Mai 20 16:17:27 ${HOSTNAME} systemd[2327]: Started Tracker file system data miner.
Mai 20 16:17:27 ${HOSTNAME} tracker-miner-f[96328]: Checking whether to crawl file system based on configured crawling interval:
Mai 20 16:17:27 ${HOSTNAME} tracker-miner-f[96328]:   Maybe (depends on a clean last shutdown)
Mai 20 16:17:27 ${HOSTNAME} tracker-miner-f[96328]: Checking whether to force mtime checking during crawling (based on last clean shutdown):
Mai 20 16:17:27 ${HOSTNAME} tracker-miner-f[96328]:   Yes 
Mai 20 16:17:43 ${HOSTNAME} tracker-miner-f[96328]: [Event Queues]  New UPDATED event: file:///home/${USER}
Mai 20 16:17:43 ${HOSTNAME} tracker-miner-f[96328]: [Event Queues] Setting up queue handlers...
Mai 20 16:17:43 ${HOSTNAME} tracker-miner-f[96328]: [Event Queues]    scheduled in idle
Mai 20 16:17:43 ${HOSTNAME} tracker-miner-f[96328]:   Notified files after 0,70 seconds
Mai 20 16:17:43 ${HOSTNAME} tracker-miner-f[96328]:   Found 52 directories, ignored 36 directories
Mai 20 16:17:43 ${HOSTNAME} tracker-miner-f[96328]:   Found 88 files, ignored 26 files
Mai 20 16:17:43 ${HOSTNAME} tracker-miner-f[96328]:   Notified files after 0,13 seconds
Mai 20 16:17:43 ${HOSTNAME} tracker-miner-f[96328]:   Found 2 directories, ignored 0 directories
Mai 20 16:17:43 ${HOSTNAME} tracker-miner-f[96328]:   Found 18 files, ignored 0 files
Mai 20 16:17:43 ${HOSTNAME} tracker-miner-f[96328]: Processing file 'file:///home/${USER}'...
Mai 20 16:17:43 ${HOSTNAME} tracker-miner-f[96328]: [Event Queues] Setting up queue handlers...
Mai 20 16:17:43 ${HOSTNAME} tracker-miner-f[96328]: [Event Queues]    cancelled: already one active
Mai 20 16:17:43 ${HOSTNAME} tracker-miner-f[96328]:   Notified files after 0,23 seconds
Mai 20 16:17:43 ${HOSTNAME} tracker-miner-f[96328]:   Found 1 directories, ignored 0 directories
Mai 20 16:17:43 ${HOSTNAME} tracker-miner-f[96328]:   Found 2 files, ignored 0 files
Mai 20 16:17:47 ${HOSTNAME} tracker-miner-f[96328]: [Event Queues]  New UPDATED event: file:///media/Daten/100-Pers%C3%B6nlich/10-Wissensverwaltung
Mai 20 16:17:47 ${HOSTNAME} tracker-miner-f[96328]: [Event Queues] Setting up queue handlers...
Mai 20 16:17:47 ${HOSTNAME} tracker-miner-f[96328]: [Event Queues]    cancelled: already one active
Mai 20 16:17:47 ${HOSTNAME} tracker-miner-f[96328]: Processing file 'file:///media/Daten/100-Pers%C3%B6nlich/10-Wissensverwaltung'...
Mai 20 16:17:47 ${HOSTNAME} tracker-miner-f[96328]: [Event Queues] Setting up queue handlers...
Mai 20 16:17:47 ${HOSTNAME} tracker-miner-f[96328]: [Event Queues]    cancelled: already one active
Mai 20 16:17:57 ${HOSTNAME} tracker-miner-f[96328]:   Notified files after 12,82 seconds
Mai 20 16:17:57 ${HOSTNAME} tracker-miner-f[96328]:   Found 5131 directories, ignored 30 directories
Mai 20 16:17:57 ${HOSTNAME} tracker-miner-f[96328]:   Found 55117 files, ignored 356 files
Mai 20 16:17:57 ${HOSTNAME} tracker-miner-f[96328]:   Notified files after 0,02 seconds
Mai 20 16:17:57 ${HOSTNAME} tracker-miner-f[96328]:   Found 0 directories, ignored 0 directories
Mai 20 16:17:57 ${HOSTNAME} tracker-miner-f[96328]:   Found 0 files, ignored 0 files
Mai 20 16:17:57 ${HOSTNAME} tracker-miner-f[96328]:   Notified files after 0,02 seconds
Mai 20 16:17:57 ${HOSTNAME} tracker-miner-f[96328]:   Found 0 directories, ignored 0 directories
Mai 20 16:17:57 ${HOSTNAME} tracker-miner-f[96328]:   Found 0 files, ignored 0 files
Mai 20 16:17:57 ${HOSTNAME} tracker-miner-f[96328]:   Notified files after 0,02 seconds
Mai 20 16:17:57 ${HOSTNAME} tracker-miner-f[96328]:   Found 0 directories, ignored 0 directories
Mai 20 16:17:57 ${HOSTNAME} tracker-miner-f[96328]:   Found 0 files, ignored 0 files
Mai 20 16:17:57 ${HOSTNAME} tracker-miner-f[96328]:   Notified files after 0,29 seconds
Mai 20 16:17:57 ${HOSTNAME} tracker-miner-f[96328]:   Found 1 directories, ignored 0 directories
Mai 20 16:17:57 ${HOSTNAME} tracker-miner-f[96328]:   Found 236 files, ignored 1 files
Mai 20 16:17:58 ${HOSTNAME} tracker-miner-f[96328]:   Notified files after 0,25 seconds
Mai 20 16:17:58 ${HOSTNAME} tracker-miner-f[96328]:   Found 1 directories, ignored 0 directories
Mai 20 16:17:58 ${HOSTNAME} tracker-miner-f[96328]:   Found 21 files, ignored 1 files
Mai 20 16:17:58 ${HOSTNAME} tracker-miner-f[96328]: [Event Queues] Setting up queue handlers...
Mai 20 16:17:58 ${HOSTNAME} tracker-miner-f[96328]: [Event Queues]    scheduled in idle
Mai 20 16:17:58 ${HOSTNAME} tracker-miner-f[96328]: Flushing SPARQL buffer, reason: Queue handlers NONE
Mai 20 16:17:58 ${HOSTNAME} tracker-miner-f[96328]: (Sparql buffer) Finished array-update with 17 tasks
Mai 20 16:17:58 ${HOSTNAME} tracker-miner-f[96328]: [Event Queues] Setting up queue handlers...
Mai 20 16:17:58 ${HOSTNAME} tracker-miner-f[96328]: [Event Queues]    scheduled in idle
Mai 20 16:17:58 ${HOSTNAME} systemd[2327]: Starting Tracker metadata extractor...
Mai 20 16:17:58 ${HOSTNAME} systemd[2327]: Started Tracker metadata extractor.

I guess ↑ this is the main problem. Is there a way to lift the restriction to $HOME?

Regards

I guess this cannot be specified by a variable, but this must be the responsible javascript:

In any case, the global search calls nautilus to search, but sticks to the general path, which is $HOME. Maybe request for a feature to call directly tracker3?

However… it seems to me that the $HOME path is hardcoded.

Okay, then there is no hope :wink:
Thanks.

Any recommendations for a good search app/gnome shell extension?

If you need to search for files, then the recommend way is the nautilus search on GNOME, which calls the tracker3 index. Since the global search with tracker3 is quite slow, the performance must be the reason why the default sticks to the current working dir recursively. So it shouldn’t be a big deal to create a shortcut at nautilus, switch to that folder and search. :wink:

Depends on the use case. If I don’t remember where I might have located the file I’d need to go to various folder and search. Therefore, a global search would be quite nice, even thought it might take longer.

If you’d have a rough idea where the file was, you’re right.

Well if it is only the filename then mlocate could be an option on the terminal.

Or maybe catfish should also do this job, which uses mlocate as backend.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.