Gnome-desktop's 'tracker' spams syslog at boot

_[5.0.9-arch1-1-ARCH with gnome-desktop 3.32.1.2-1 and tracker 2.2.1]_ My syslog at boot ($ sudo journalctl -b) is being spammed by messages about tracker-miner not being able to execute sparql along with the tracker-store.service unit being masked. I do not remember masking this unit. Very small extract below: Apr 26 07:47:05 HOSTNAME dbus-daemon: [session uid=1000 pid=3165] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.54' (uid=1000 pid=3441 comm="/usr/lib/tracker-miner-fs ") Apr 26 07:47:05 HOSTNAME dbus-daemon: [session uid=1000 pid=3165] Activation via systemd failed for unit 'tracker-store.service': Unit tracker-store.service is masked. Apr 26 07:47:05 HOSTNAME tracker-miner-f: (Sparql buffer) Error in array-update: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit tracker-store.service is masked. Apr 26 07:47:05 HOSTNAME tracker-miner-f: Could not execute sparql: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit tracker-store.service is masked. Apr 26 07:47:05 HOSTNAME dbus-daemon: [session uid=1000 pid=3165] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.54' (uid=1000 pid=3441 comm="/usr/lib/tracker-miner-fs ") Apr 26 07:47:05 HOSTNAME dbus-daemon: [session uid=1000 pid=3165] Activation via systemd failed for unit 'tracker-store.service': Unit tracker-store.service is masked. Apr 26 07:47:05 HOSTNAME tracker-miner-f: (Sparql buffer) Error in array-update: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit tracker-store.service is masked. I also see: $ systemctl --user status tracker-store ● tracker-store.service Loaded: masked (Reason: Unit tracker-store.service is masked.) Active: inactive (dead) and $ tracker status Currently indexed: 50073 files, 3018 folders Remaining space on database partition: 39.0 GB (24.28%) (tracker status:17788): Tracker-CRITICAL **: 19:47:02.875: Could not get miner progress for 'org.freedesktop.Tracker1.Miner.Extract': Timeout was reached (tracker status:17788): Tracker-CRITICAL **: 19:47:27.899: Could not get miner progress for 'org.freedesktop.Tracker1.Miner.Files': Timeout was reached All data miners are idle, indexing complete indicating that indeed the service unit is masked and its has completed its indexing job. Quite diverse posts involve similar keywords as what appears in the boot syslog: "tracker-miner"(1 ), "sparql" not executing (2 ), a masked "tracker-store.service" unit (3 ). tracker has been held responsible for monopolizing CPU , hogging memory and storage space , violating user privacy, etc, ever since it started shipping systematically as part of gnome-desktop. No post got me closer to answering:
- Why do I get those syslog messages at boot ?
Note: Log verbosity is minimum and set to "errors" by default for all tracker apps. I don't know how to reduce it to nil. I also assume (perhaps wrongly) that if tracker was well configured, it would not be at the origin of so many error messages at boot.
- If so, what do I need to fix/reconfigure for those errors to go away ?