I keep having tons of these in syslog

2024-04-23T04:55:28.315700+02:00 tucano gvfsd-network[318402]: GFileInfo created without standard::content-type
2024-04-23T04:55:28.315722+02:00 tucano gvfsd-network[318402]: file ../../../gio/gfileinfo.c: line 1822 (g_file_info_get_content_type): should not be reached
2024-04-23T04:55:28.315743+02:00 tucano gvfsd-network[318402]: g_ref_string_new_intern: assertion 'str != NULL' failed
 [ the above three lines are repeated 63 times in the space of 50 ms ]
2024-04-23T04:21:41.887252+02:00 tucano gvfsd-wsdd[1507271]: Failed to spawn the wsdd daemon: Failed to execute child process “wsdd” (No such file or directory)
2024-04-23T04:21:41.887324+02:00 tucano gvfsd-network[318402]: Couldn't create directory monitor on wsdd:///. Error: Automount failed: Failed to spawn the underlying wsdd daemon.
2024-04-23T04:21:41.891620+02:00 tucano gvfsd-network[318402]: g_ref_string_release: assertion 'str != NULL' failed
 [ the above line is repeated 64 times in the space of 15 ms ]

The above sequence is repeated every 15 s

This has gone on for 6 days, until I killed the gvfsd-network process.  Six days ago I had
rebooted the machine after some months running because I could not stop it and I suspected some
library needing reboot, but apparently this is not the case.

This should be fixed by 1.54.x from unstable, when it migrates to testing
(upstream commit "wsdd: Print debug info only if GVFS_WSDD_DEBUG is set").
That's currently blocked by the 64-bit time_t transition, but according to
the latest update from the release team, packages should start migrating
again soon.

This might be fixed by 1.54.x too.

    smcv

Ok, thanks