https://bugs.kde.org/show_bug.cgi?id=487719
Andrey <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #12 from Andrey <[email protected]> --- Hey folks! Just wanted to say thanks for KDE Connect - it's awesome. I noticed a regression in device discovery and traced it to the switch from Avahi to a new standalone mDNS library. My phone isn't being discovered anymore. I compiled the mDNS CLI https://github.com/mjansson/mdns/blob/main/mdns.c and tested it directly. It fails to detect one of my phones - only finding two devices (including itself) - while avahi-discover sees all devices correctly, including my main phone. To rule out conflicts, I also started and stopped avahi-daemon during testing and checked the ports in use with the program shown, confirming there’s no interference between avahi-daemon and kdeconnectd running simultaneously. Additionally, the mDNS library seems to have unresolved issues and very limited upstream activity: https://github.com/mjansson/mdns/issues/60 https://github.com/mjansson/mdns/issues/92 I appreciate the move toward cross-platform compatibility, but this might warrant reconsideration or a fallback mechanism using Avahi. Let me know if logs or test output would help. -- You are receiving this mail because: You are watching all bug changes.
