This is supposed to act on the command that you provide tracker, which does not exist.
Find the specific command:
pgrep -a tracker
and either kill 9 the PID, or killall <command_name>.
OTOH, I would check more about this, with htop, or other process manager, to see what it is doing.
Actually, using htop, you can also do the above (find and kill)
I experienced the same issue the last couple of days. I am using gnome since a long time now. But this problem with CPU load for tracker-miner-fs-3 just started some days ago. Must have something to do with a recent update.
I also saw multiple coredumps related to the miner and the extract tool:
╰─# coredumpctl --no-pager
TIME PID UID GID SIG COREFILE EXE SIZE
Sat 2023-03-18 23:21:14 CET 10041 1000 1000 SIGSEGV missing /usr/lib/tracker-miner-fs-3 -
Sat 2023-03-18 23:21:48 CET 10616 1000 1000 SIGSEGV missing /usr/lib/tracker-miner-fs-3 -
Sat 2023-03-18 23:21:58 CET 10791 1000 1000 SIGSEGV missing /usr/lib/tracker-miner-fs-3 -
Sat 2023-03-18 23:22:39 CET 11158 1000 1000 SIGSEGV missing /usr/lib/tracker-miner-fs-3 -
Wed 2023-03-22 10:50:09 CET 23349 1000 1000 SIGSEGV present /usr/lib/tracker-miner-fs-3 327.1K
Wed 2023-03-22 10:51:38 CET 24594 1000 1000 SIGSEGV present /usr/lib/tracker-miner-fs-3 326.5K
Wed 2023-03-22 10:53:46 CET 25964 1000 1000 SIGSEGV present /usr/lib/tracker-miner-fs-3 326.0K
Wed 2023-03-22 11:02:11 CET 15386 1000 1000 SIGSEGV present /usr/lib/tracker-extract-3 12.9M
Wed 2023-03-22 11:02:12 CET 34172 1000 1000 SIGSEGV present /usr/lib/tracker-extract-3 8.6M
Wed 2023-03-22 12:54:07 CET 9728 1000 1000 SIGSEGV present /usr/lib/tracker-extract-3 14.4M
Wed 2023-03-22 12:54:07 CET 209760 1000 1000 SIGSEGV present /usr/lib/tracker-extract-3 4.9M
Wed 2023-03-22 13:15:03 CET 209872 1000 1000 SIGSEGV present /usr/lib/tracker-extract-3 13.0M
Wed 2023-03-22 14:25:03 CET 373400 1000 1000 SIGSEGV present /usr/lib/tracker-extract-3 13.7M
Wed 2023-03-22 15:05:03 CET 933355 1000 1000 SIGSEGV present /usr/lib/tracker-extract-3 13.7M
Then I saw in the journal that the miner has some issue with specific AVI files in a specific folder. The error messages look like this
tracker-extract: Failed to update ignored file 'file:///myfolder/DSCFxxxx.AVI':
I found thousands of them in the log. I used dconf-editor to put *.AVI files on the exclusion list and I renamed that folder. Now the CPU load issue does not occur anymore.
I mean it could be a Bug related to avi file format indeed.
I can try reproducing.
And as a hint if you do not use Gnome apps like music and documents and you arte not browsing/searching a huge bunch of files over the filebrowser itself you can sevely disable the tracker-miner.
It appears that Gnome Tracker is a core part of Gnome and is hard to eliminate,
but you might be interested in the How can I disable Tracker in GNOME? section.
I actually do not want to disable it. I like the functionality it offers. I am an in the file manager nautilus and do a search, it not only searches for filenames but also for file content.
In the meantime I have reverted the changes I mentioned earlier. I removed *.AVI from the file exclusion list (in fact I am using default exclusions again) and I renamed the folder with the AVI files back to its original name. I rebooted and everything is normal. No CPU load.
I get a core dump every time I do a “tracker3 info ...” on a movie file. If it is mkv, mp4 or avi. Is that the same for you?
╰─# tracker3 info Steve-Jobs.mkv
Querying information for entity: 'Steve-Jobs.mkv'
No metadata available for that URI
Data object ?/data/media/Filme/MKV/Steve-Jobs.mkv? currently exists
╰─# LANG=C tracker3 status
Currently indexed: 11009 files, 892 folders
Remaining space on database partition: 317,8?GB (78,52%)
All data miners are idle, indexing complete
2 recorded failures
Path Message
?path/f0598c6dfaee4909b1169b822035e537.gif Could not get any metadata for uri:'file:///home/matthias/Dokumente/?
/path-in-home//xyzxyz.pdf ?ms.tex? is not an absolute IRI