https://bugs.kde.org/show_bug.cgi?id=522542
Bug ID: 522542
Summary: Windows daemon hangs after pairing with Pixel 9 Pro;
CLI becomes unresponsive
Classification: Applications
Product: kdeconnect
Version First 26.04.3
Reported In:
Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
Severity: normal
Priority: NOR
Component: desktop-application
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
DESCRIPTION
After pairing KDE Connect for Windows with my Pixel 9 Pro, KDE Connect becomes
unresponsive. The phone reports "Timed out". The Windows app does not always
visibly crash, but kdeconnect-cli --list-devices hangs indefinitely after
pairing.
This occurs with both:
- Microsoft Store build KDEe.V.KDEConnect_26.402.6289.0
- KDE Connect Windows offline installer 26.04.3
STEPS TO REPRODUCE
1. Install KDE Connect on Windows.
2. Clear previous KDE Connect pairing state on both Windows and Android.
3. Start KDE Connect on Windows.
4. Start KDE Connect on Android on a Pixel 9 Pro.
5. Pair the devices.
6. Wait for pairing/plugin negotiation to complete.
OBSERVED RESULT
The phone reports "Timed out". On Windows, KDE Connect becomes stuck after
pairing. kdeconnect-cli --list-devices hangs and does not return.
In the Store build, Windows Event Viewer logged kdeconnectd.exe crashes:
- Faulting application: kdeconnectd.exe
- Faulting module: ntdll.dll
- Exception code: 0xc00000fd
- Example fault offset: 00000000000466bb
With the offline installer, the daemon may remain running but its local control
path is unresponsive.
EXPECTED RESULT
The devices should pair successfully and kdeconnect-cli --list-devices should
return the paired/reachable device.
SOFTWARE/HARDWARE DETAILS
Windows:
- Windows 10 Home
- NT version: 10.0.26200.0
- KDE Connect offline installer: 26.04.3
- KDE Connect Store package previously tested: KDEe.V.KDEConnect_26.402.6289.0
Android:
- Pixel 9 Pro
- KDE Connect protocol version reported in trusted_devices: 8
- Phone device ID: 19c596b2422143ba80eaf58310968062
Network:
- Windows IP: 192.168.0.17
- Phone IP: 192.168.0.197
- TCP connection to port 1716 is established successfully
- Windows network profile is Private
- Windows firewall rules allow KDE Connect TCP/UDP 1714-1764
ADDITIONAL INFORMATION
The issue does not appear to be basic discovery or firewall failure. Windows
can discover the phone and establishes TCP connections on port 1716. The hang
appears to happen after trust/pairing is written and plugin/device negotiation
begins.
Tried:
- Reinstalling Store version
- Resetting Windows-side KDE Connect app data
- Clearing/recreating Android-side pairing identity
- Installing offline Windows installer
- Disabling Windows-side clipboard autosync
- Restarting kdeconnectd, kdeconnect-app, kdeconnect-indicator, and bundled
dbus-daemon
The problem still reproduces.
--
You are receiving this mail because:
You are watching all bug changes.
