Just a wild guess: Maybe avahi-daemon is involved somehow? For me at least these annoying messages seem to have stopped completely after throwing out the avahi-daemon service (for other reasons).
So you may try this:
systemctl disable avahi-daemon.socket avahi-daemon.service
If it helps, do this:
systemctl mask avahi-daemon.socket avahi-daemon.service systemctl stop avahi-daemon.socket avahi-daemon.service
Just a wild guess: Maybe avahi-daemon is involved somehow? For me at least these annoying messages seem to have stopped completely after throwing out the avahi-daemon service (for other reasons).
So you may try this:
systemctl disable avahi-daemon.socket avahi-daemon. service
If it helps, do this:
systemctl mask avahi-daemon.socket avahi-daemon. service service
systemctl stop avahi-daemon.socket avahi-daemon.