Control: retitle -1 wsdd: ValueError: badly formed hexadecimal UUID string
Control: reassign -1 wsdd
Control: affects -1 + gvfs-daemons
On Mon, 16 Feb 2026 at 07:49:59 +0100, Francesco Potortì wrote:
I see this in syslog, with apparently no consequence
7.9516 gvfsd: 2026-02-15 04:52:17,950:asyncio ERROR(pid 44919): Exception in
callback MulticastHandler.read_socket()
7.9517 gvfsd: handle: <Handle MulticastHandler.read_socket()>
7.9517 gvfsd: Traceback (most recent call last):
7.9517 gvfsd: File "/usr/lib/python3.13/asyncio/events.py", line 89, in _run
7.9517 gvfsd: self._context.run(self._callback, *self._args)
7.9517 gvfsd: ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
7.9517 gvfsd: File "/usr/bin/wsdd", line 330, in read_socket
7.9518 gvfsd: handler.handle_packet(msg.decode('utf-8'), address)
7.9518 gvfsd: ~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
7.9518 gvfsd: File "/usr/bin/wsdd", line 742, in handle_packet
7.9518 gvfsd: self.handle_message(msg, src)
7.9518 gvfsd: ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^
7.9518 gvfsd: File "/usr/bin/wsdd", line 534, in handle_message
7.9518 gvfsd: retval = handler(header, body)
7.9518 gvfsd: File "/usr/bin/wsdd", line 769, in handle_hello
7.9519 gvfsd: self.perform_metadata_exchange(endpoint, xaddr)
7.9519 gvfsd: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
7.9519 gvfsd: File "/usr/bin/wsdd", line 857, in perform_metadata_exchange
7.9519 gvfsd: self.handle_metadata(stream.read(), endpoint, xaddr)
7.9519 gvfsd: ~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
7.9519 gvfsd: File "/usr/bin/wsdd", line 866, in handle_metadata
7.9519 gvfsd: device_uuid = str(uuid.UUID(endpoint))
7.9520 gvfsd: ~~~~~~~~~^^^^^^^^^^
7.9520 gvfsd: File "/usr/lib/python3.13/uuid.py", line 181, in __init__
7.9520 gvfsd: raise ValueError('badly formed hexadecimal UUID string')
7.9520 gvfsd: ValueError: badly formed hexadecimal UUID string
This appears to be logged by wsdd (which gvfsd runs as a subprocess if
available) rather than by gvfsd itself: reassigning.
Probably this indicates that some device on your network has an invalid
UUID, or a UUID in a format that wsdd wasn't expecting, and wsdd should
perhaps be more robust against that.
smcv