Bug#1069751: gvfs-daemons: gvfsd-network fills the logs with errors

[Simon McVittie]

On Wed, 24 Apr 2024 at 09:24:14 +0200, Francesco Potortì wrote:
> 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.
> 
> The above sequence is repeated every 15 s

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.

> 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

This might be fixed by 1.54.x too.

    smcv