you are simply wrong here and should blame your distribution for such an old systemd which still links to the devel mailing list just because a random service fails
in case of "Failed to start Tracker metadata" systemd is only the messenger Am 10.10.18 um 00:33 schrieb g.david...@gmail.com: > salve a tutti. Hoaftto un test sulla mia distribuzione Manjaro ed ho ricevuto > questo messaggio di errore:[gaetanodavide@gaetanodavide-pc ~]$ sudo systemctl > --failed > [sudo] password di gaetanodavide: > 0 loaded units listed. Pass --all to see loaded but inactive units, too. > To show all installed unit files use 'systemctl list-unit-files'. > [gaetanodavide@gaetanodavide-pc ~]$ sudo journalctl -p 3 -xb > -- Logs begin at Mon 2018-10-08 21:22:28 CEST, end at Wed 2018-10-10 00:04:55 > C> > ott 09 23:09:36 gaetanodavide-pc kernel: tpm_crb MSFT0101:00: [Firmware Bug]: > A> > ott 09 23:09:36 gaetanodavide-pc kernel: tpm_crb MSFT0101:00: [Firmware Bug]: > A> > ott 09 23:10:04 gaetanodavide-pc bluetoothd[367]: RFCOMM server failed for > Head> > ott 09 23:10:04 gaetanodavide-pc bluetoothd[367]: RFCOMM server failed for > :1.1> > ott 09 23:10:13 gaetanodavide-pc systemd[883]: Failed to start Tracker > metadata> > -- Subject: L'unità UNIT è fallita > -- Defined-By: systemd > -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
