# Revision history [back]

First of all, I am running Fedora 20 on a desktop system with the development features and gnome 3. It wasn't long after I began that I noticed lack of keyboard response bordering on no keyboard at all so I looked and found that my disk light was on continuously. Realizing from past experience that this is the tracker-miner, I looked for it and found it in the system monitor.

I haven't seen any disadvantage to simply (as root) removing permissions from the executables in /bin/track* and /usr/libexec/track* but a subsequent update did reverse my actions. That does not mean that there were or are disadvantages although all the applications I used (Firefox, Thunderbird, Libre Office and a vew utilities) don't seem to suffer. YMMV.

Recently I decided to try another tactic and apparently I have succeeded in reducing the hold on my system. I used several changes and then restored the correct permissions to the executables.

(1.) I ran "gnome-session-properties" from a terminal which did not show tracker and so was dismissed. No help there.

(2.) I ran "tracker-preferences" from a terminal which is more helpful.

  I unchecked

"Monitor file and directory changes" so it will not monitor those and try to read the changed files and update the database in real time.

I clicked the radio button for

Index content in the background:

* Only when the computer is not being used.

These two changes alone seem to have stopped the dominance of tracker.  I changed nothing else with this tool.


(3.) I also changed these files: ~/.config/autostart/tracker* but primarily tracker-miner-fs.desktop and tracker-store.desktop: In tracker-miner-fs.desktop, I removed the foreign language names and added some options to the executable line:

  Exec="/usr/libexec/tracker-miner-fs --no-daemon --disable-miner=Applications --disable-miner=Userguides"

In tracker-store.desktop, I also removed the foreign language names and added an option to the executable:

Exec="/usr/libexec/tracker-store --low-memory"

It should not matter how much memory I actually have (2GB) or if I add more.


(4.) Finally, I needed to do a hard-reset of tracker and restart it as root which went like this:

 sudo tracker-control -t  # properly terminates tracker processes without damaging any data (hopefully)

sudo tracker-control -r  # kills any remaining processes and removes the databases

sudo tracker-control --start # starts miner processes and tracker-store


Perhaps not all of #4 needs to be run as root, but it's better to be safe.

So far, (just a few hours) I'm quite pleased again have control of my computer!

Please, if you try this, post here if it does not work for you. Remember, this is for a gnome (3) system. If you favor kde, there's a different path for you to follow.

DON'T TRY THIS YET unless you are brave. I'm still checking out an issue. First of all, I am running Fedora 20 on a desktop system with the development features and gnome 3. It wasn't long after I began that I noticed lack of keyboard response bordering on no keyboard at all so I looked and found that my disk light was on continuously. Realizing from past experience that this is the tracker-miner, I looked for it and found it in the system monitor.

I haven't seen any disadvantage to simply (as root) removing permissions from the executables in /bin/track* and /usr/libexec/track* but a subsequent update did reverse my actions. That does not mean that there were or are disadvantages although all the applications I used (Firefox, Thunderbird, Libre Office and a vew utilities) don't seem to suffer. YMMV.

Recently I decided to try another tactic and apparently I have succeeded in reducing the hold on my system. I used several changes and then restored the correct permissions to the executables.

(1.) I ran "gnome-session-properties" from a terminal which did not show tracker and so was dismissed. No help there.

(2.) I ran "tracker-preferences" from a terminal which is more helpful.

  I unchecked

"Monitor file and directory changes" so it will not monitor those and try to read the changed files and update the database in real time.

I clicked the radio button for

Index content in the background:

* Only when the computer is not being used.

These two changes alone seem to have stopped the dominance of tracker.  I changed nothing else with this tool.


(3.) I also changed these files: ~/.config/autostart/tracker* but primarily tracker-miner-fs.desktop and tracker-store.desktop: In tracker-miner-fs.desktop, I removed the foreign language names and added some options to the executable line:

  Exec="/usr/libexec/tracker-miner-fs --no-daemon --disable-miner=Applications --disable-miner=Userguides"

In tracker-store.desktop, I also removed the foreign language names and added an option to the executable:

Exec="/usr/libexec/tracker-store --low-memory"

It should not matter how much memory I actually have (2GB) or if I add more.


(4.) Finally, I needed to do a hard-reset of tracker and restart it as root which went like this:

 sudo tracker-control -t  # properly terminates tracker processes without damaging any data (hopefully)

sudo tracker-control -r  # kills any remaining processes and removes the databases

sudo tracker-control --start # starts miner processes and tracker-store


Perhaps not all of #4 needs to be run as root, but it's better to be safe.

So far, (just a few hours) I'm quite pleased again have control of my computer!

Please, if you try this, post here if it does not work for you. Remember, this is for a gnome (3) system. If you favor kde, there's a different path for you to follow.

DON'T TRY THIS YET unless [See my Post Script at the bottom if you are brave. I'm still checking out an issue. have read this before.] First of all, I am running Fedora 20 on a desktop system with the development features and gnome 3. It wasn't long after I began that I noticed lack of keyboard response bordering on no keyboard at all so I looked and found that my disk light was on continuously. Realizing from past experience that this is the tracker-miner, I looked for it and found it in the system monitor.

I haven't seen any disadvantage to simply (as root) removing permissions from the executables in /bin/track* and /usr/libexec/track* but a subsequent update did reverse my actions. That does not mean that there were or are disadvantages although all the applications I used (Firefox, Thunderbird, Libre Office and a vew utilities) don't seem to suffer. YMMV.

Recently I decided to try another tactic and apparently I have succeeded in reducing the hold on my system. I used several changes and then restored the correct permissions to the executables.

(1.) I ran "gnome-session-properties" from a terminal which did not show tracker and so was dismissed. No help there.

(2.) I ran "tracker-preferences" from a terminal which is more helpful.

  I unchecked

"Monitor file and directory changes" so it will not monitor those and try to read the changed files and update the database in real time.

I clicked the radio button for

Index content in the background:

* Only when the computer is not being used.

These two changes alone seem to have stopped the dominance of tracker.  I changed nothing else helpful, but after a trial with this tool.

my mods, went back to the defaults. See the Post Script. **

(3.) I also changed these files: ~/.config/autostart/tracker* but primarily tracker-miner-fs.desktop and tracker-store.desktop: In tracker-miner-fs.desktop, I removed the foreign language names and added some options to the executable line:

  Exec="/usr/libexec/tracker-miner-fs --no-daemon --disable-miner=Applications --disable-miner=Userguides"

In tracker-store.desktop, I also removed the foreign language names and added an option to the executable:

Exec="/usr/libexec/tracker-store --low-memory"

It should not matter how much memory I actually have (2GB) or if I add more.


(4.) Finally, I needed to do a hard-reset of tracker and restart it as root which went like this:

 sudo tracker-control -t  # properly terminates tracker processes without damaging any data (hopefully)

sudo tracker-control -r  # kills any remaining processes and removes the databases

sudo tracker-control --start # starts miner processes and tracker-store


Perhaps not all of #4 needs to be run as root, but it's better to be safe.

So far, (just a few hours) I'm quite pleased again have control of my computer!

Please, if you try this, post here if it does not work for you. Remember, this is for a gnome (3) system. If you favor kde, there's a different path for you to follow.

**Post Script: I did have a problem with yumex for some reason and I could not remove it. Except for telling tracker that I have low memory - which seems to help considerably, by the way - I went back to the defaults in tracker-preferences. Rebooting seems to have helped with not being able to use yumex - I also removed and re-installed yumex. Tracker seems to behave now with the "low memory" option per above. There is one tracker-childtask, tracker-store is using 1%-2% CPU and tracker-miner-fs is showing "0" percent CPU usage. The disk light is on continuously right now and I'm seeing an occasional small hesitation in the gnome GUI but overall the system seems quite usable. Even more interesting, I now have a "Search and Indexing" icon in docky. I will add an edit or a new post if I see a change.