This floods systemd's log, around 10 messages per second.
At first glance, the commit mentioned above seem relevant.
Even if a proper fix takes time to be incorporated, I'd be happy with a workaround, but am clueless where to start man gvfds-metadata offers no relevant option. Killing gvfsd-metadata only yields another one. Parent process is systemd. Disabling /usr/lib/systemd/user/gvfs-metadata.service will probably break file managers, filesystem mounts and the like. Any hint appreciated.
Still observed here.
This floods systemd's log, around 10 messages per second.
At first glance, the commit mentioned above seem relevant.
Even if a proper fix takes time to be incorporated, I'd be happy with a workaround, but am clueless where to start man gvfds-metadata offers no relevant option. Killing gvfsd-metadata only yields another one. Parent process is systemd. Disabling /usr/lib/ systemd/ user/gvfs- metadata. service will probably break file managers, filesystem mounts and the like. Any hint appreciated.
Thanks.