Although I have created .nomedia and .trackerignore under the directory ~/Documents/Archive, tracker-miner-fs-3 seems to completely ignored those two tracker-ignore files and consistently want to search and index the directory, I have SELinux enabled and I didn’t grant it such permission (because I don’t want to) so it just keeps trying and fail and return, is tracker no longer respecting trackerignore now?
I don’t know SELinux at all.
If SELinux is preventing tracker.miner to access the directory Archive, won’t tracker-miner find itself unable to see the “Archive/.nomedia” file, making its presence irrelevant?
Note that the warnings you get come from GLib itself, if tracker-miner-fs-3 does not stop processing the folder it is because it doesn’t ever get an error propagated, and likewise if GLib does not stop and propagate an error, it is most likely because the kernel it not raising an error but giving it incomplete data instead. This is just one of the many possible outcomes if you mess with software at the system call level. Very few software projects, if any, will consider this a supported situation.
Tracker-miners 3.6.x available with GNOME 45 might help you, since it changed so the files declared at the ignored-directories-with-content setting are stat()-ed directly, instead of found through opendir()/readdir(). Or it might not, depending on the selinux rules.
Or you could grant the permission, and let tracker-miner-fs-3/glib find the .nomedia/.trackerignore files so they can be honored.