https://bugs.kde.org/show_bug.cgi?id=516214
Bug ID: 516214
Summary: KDE Connect ≥ 1.34.4 fails to discover devices on LAN
(regression in network discovery) — works only via
hotspot
Classification: Applications
Product: kdeconnect
Version First unspecified
Reported In:
Platform: Manjaro
OS: Linux
Status: REPORTED
Severity: grave
Priority: NOR
Component: android-application
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
Target Milestone: ---
STEPS TO REPRODUCE
Install KDE Connect version 1.34.4 or newer on Linux PC and Android device.
Connect both devices to the same local network:
PC via Ethernet + Android via Wi-Fi
Both via Wi-Fi (also tested).
Open KDE Connect on both devices.
Check the list of available devices.
OBSERVED RESULT
After version 1.34.4, KDE Connect no longer discovers devices on a normal LAN.
Symptoms:
No new devices appear for pairing.
Only previously paired devices may appear.
kdeconnect-cli -l shows only already paired devices.
The output typically shows:
1 device found
even when multiple devices are present on the network.
The issue persists even after:
Clearing all data on Android
Removing all KDE Connect configs on Linux
Reinstalling KDE Connect
Testing with another Android phone
Testing with another Linux PC
Testing from a Live CD Manjaro KDE (clean environment)
Therefore, this does not appear to be a local configuration issue.
EXPECTED RESULT
Devices connected to the same LAN should be automatically discovered via
broadcast/mDNS and appear available for pairing.
REGRESSION
Yes.
Discovery works correctly in versions before 1.34.4
Stops working starting with 1.34.4 and later
SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux
KDE Plasma Version: 6.5.5
KDE Frameworks Version: 6.22.0
Qt Version: 6.10.1
Kernel Version: 6.18.8-1-MANJARO (64-bit)
Graphics Platform: X11
KDE Connect (Linux): ≥ 1.34.4
KDE Connect (Android): Latest Play Store version
Hardware:
CPU: AMD Ryzen 7 1700
RAM: 32 GB
GPU: NVIDIA GeForce GTX 960
NETWORK ENVIRONMENT
Tested scenarios:
PC connected via Ethernet + Android via Wi-Fi
Both devices connected via Wi-Fi
Multiple different routers tested
Firewall disabled (firewalld stopped)
No VPN or guest network involved
Devices confirmed to be on the same subnet
Additional tests:
✔ Works normally when using an Android hotspot network
✔ Manual UDP communication tested successfully in both directions
✔ Broadcast UDP test confirmed working at the network level
This strongly suggests a discovery mechanism issue, not a general network
connectivity problem.
ADDITIONAL INFORMATION
The issue affects device discovery only:
Direct UDP communication works normally
Only KDE Connect automatic discovery fails
Behavior is consistent across clean systems (Live CD)
Appears to be a regression introduced after 1.34.4
Running:
kdeconnect-cli -l
only shows already paired devices, never new ones.
As a temporary workaround, I manually downgraded the Android KDE Connect app by
installing version 1.34.4 from F-Droid.
After downgrading, device discovery immediately started working again on the
same LAN, without any other configuration changes.
This strongly indicates a regression introduced in versions newer than 1.34.4.
POSSIBLE ROOT CAUSE (OBSERVATION)
The behavior suggests a regression in network interface selection or discovery
handling introduced after version 1.34.4.
Discovery works normally on simple networks (hotspot), but fails on real LAN
environments, which may indicate:
Interface binding changes
Broadcast/mDNS discovery regression
Network interface filtering issues
DEBUG INFORMATION
Systemd logs show no dedicated service since kdeconnectd runs via DBus.
Relevant command output:
journalctl --user -u kdeconnect -b
-- No entries --
This appears expected behavior for current versions.
--
You are receiving this mail because:
You are watching all bug changes.
