Package: kdeconnect Version: 25.04.2-1+deb13u1 Severity: important X-Debbugs-Cc: [email protected]
Kdeconnect causes mDNS address publishing services (systemd-resolved, avahi-daemon) to change the published hostname and therefore break discoverability and connectivity using the known hostname. After a user session has logged in and as a result the user session service has started: [email protected] Restarting systemd-resolved (that is managing mDNS publishing) breaks host discovery due to: E495-A systemd-resolved[65393]: Detected conflict on E495-A.local IN AAAA fe80::9a7d:5041:7b61:53fd E495-A systemd-resolved[65393]: Hostname conflict, changing published hostname from 'E495-A' to 'E495-A5'. Checking the ports shows kdeconnect is using 5353: tj@E495-A:~$ sudo ss -tunlp 'sport = 5353' Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port Process udp UNCONN 0 0 0.0.0.0:5353 0.0.0.0:* users:(("systemd-resolve",pid=65769,fd=15)) udp UNCONN 0 0 [::]:5353 [::]:* users:(("systemd-resolve",pid=65769,fd=16)) udp UNCONN 0 0 *:5353 *:* users:(("kdeconnectd",pid=66103,fd=20)) I found upstream reports about this that also affects avahi-daemon in the same way. https://bugs.kde.org/show_bug.cgi?id=487719 The workaround is to stop the kdeconnect user session service before restarting resolved/avahi and start it after. -- System Information: Debian Release: 13.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'stable'), (100, 'proposed-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 7.0.9+debian+tj (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
