KDE Connect Version: 1.0.2 This always happens since I upgrade Qt-5 from 5.8.0 to 5.9.0. >> QNativeSocketEngine::bind() was not called in QAbstractSocket::UnconnectedState << Log: ``` 21:53:48 kdeconnectd[1270]: kdeconnect.core: Broadcasting identity packet 21:53:48 kdeconnectd[1270]: QNativeSocketEngine::bind() was not called in QAbstractSocket::UnconnectedState 21:53:52 kdeconnectd[1270]: kdeconnect.core: Sending onNetworkChange to 1 LinkProviders 21:53:52 kdeconnectd[1270]: kdeconnect.core: Broadcasting identity packet 21:53:52 kdeconnectd[1270]: QNativeSocketEngine::bind() was not called in QAbstractSocket::UnconnectedState 21:53:55 kdeconnectd[1270]: kdeconnect.core: Sending onNetworkChange to 1 LinkProviders 21:53:55 kdeconnectd[1270]: kdeconnect.core: Broadcasting identity packet 21:53:55 kdeconnectd[1270]: QNativeSocketEngine::bind() was not called in QAbstractSocket::UnconnectedState ``` Network: ``` 95 131.063031253 192.168.1.103 → 192.168.1.109 UDP 861 39351 → 1716 Len=819 96 131.063408694 192.168.1.103 → 192.168.1.109 UDP 861 39351 → 1714 Len=819 97 131.063466932 192.168.1.109 → 192.168.1.103 ICMP 590 Destination unreachable (Port unreachable) ``` Connection: ``` lion@Lion-Laptop [ ~ ] $ ss --listen --udp --tcp --numeric | grep 171 udp UNCONN 0 0 *:1716 *:* tcp LISTEN 0 50 :::1716 :::* ```
Not that this is not a problem, but I've been using Qt 5.9 for a while and I haven't experienced this issue. Is it a normal local network?
(In reply to Aleix Pol from comment #1) > Not that this is not a problem, but I've been using Qt 5.9 for a while and I > haven't experienced this issue. > > Is it a normal local network? Yes, absolute, reproducible on other network (WiFi) with my laptop. Investigating... Another strange thing is, most of the time I click the 'Refresh' or 'Request Pair' on the control panel, there is no any network flow. The former says > kdeconnect.core: Sending onNetworkChange to 1 LinkProviders > kdeconnect.core: Broadcasting identity packet > QNativeSocketEngine::bind() was not called in QAbstractSocket::UnconnectedState , the latter says > Device pairing error "Device not reachable"
Okay. I found KDE Connect uses proxy... until now. It's astonishing. Another issue is KDE Connect sticks with the old proxy setting, after I changed proxy setting in System Settings. Until I restart my session (logout-and-login).
Marking this RESOLVED and splitting it into two... #382037 and #382038