https://bugs.kde.org/show_bug.cgi?id=487719
--- Comment #21 from Sergio <[email protected]> --- Newer versions of kdeconnectd are said to have an autodetection logic to "if [avahi] is not running, we will fall back to our own mdns implementation." This is said to be to work around the fact that avahi has no dbus activation. The problem is that this autodetection logic appears not to be working properly, so that kdeconnectd binds to 5353 and starts its own mdns even when avahi is running. A trivial situation capable of triggering issues is restarting the avahi-daemon, which causes the restarted daemon to find another mdns stack already running. I am sure there are others, because I have experienced kdeconnect seize the mdns operation breaking the .local network even without restarting avahi-daemon. The current behavior is somehow even worse than the previous one. Previously, kdeconnect was systematically taking mdns control, which lead distro to have packages fully disabling mdns from kdeconnect (e.g., kdeconnect-no-mdns). Now the problem is totally erratic and avahi breakage can occur days after system startup. Please provide a proper fix: either have a config file entry to fully disable mdns or a command line option. Incidentally, what do you mean by "missing dbus activation" for avahi? -- You are receiving this mail because: You are watching all bug changes.
