Description of problem: I've a spinning disk (not ssd) and a tons of large machine learning datasets in ~/Downloads When tracker-miner-fs works my machine is almost unresponsive at all (I have to power cycle it) The settings in the UI seems to be where to search not where to crawl there is no easy way to disable filesystem crawling the should_crawl function tracker-main.c seems to return false if interval is set to -2 https://gitlab.gnome.org/GNOME/tracker-miners/blob/master/src/miners/fs/tracker-main.c#L199 so the following should disable it gsettings set org.freedesktop.Tracker.Miner.Files crawling-interval -2 but it did not Version-Release number of selected component (if applicable): tracker-miners-2.1.4-1.fc28.x86_64 How reproducible: always Steps to Reproduce: gsettings set org.freedesktop.Tracker.Miner.Files crawling-interval -2 Actual results: filesystem crawling is still freezing my laptop Expected results: disable filesystem crawling Additional info: good to have 1. a UI to permanently stop crawling and an indicator that it's currently running in background 2. a queue with max limit (that forces the process to sleep until consumer is done) https://docs.python.org/2/library/queue.html#Queue.Queue
Created attachment 1501279 [details] screenshot of another case having tracker running
I've made the value of "/org/freedesktop/tracker/miner/files/index-recursive-directories" and "/org/freedesktop/tracker/miner/files/index-single-directories" to be empty array [] and got tracker-store running. I'll report if miner-fs is also still running.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.