https://bugs.kde.org/show_bug.cgi?id=471313
--- Comment #3 from Pedro V <voidpointertonull+bugskde...@gmail.com> --- I'm guessing that in both cases the issue is with broadcasting though, just not sure how would that happen in the hotspot case with just one interface. Maybe there are multiple interfaces in that case too even if they are not connected to the same network, or there are interfaces not considered by the users as they may not belong to physical connections. Look at the findings I described in bug 470085 , you might have the same issue, and it's actually not hard to check, it's not even necessary to disconnect anything, the "Refresh" menu point on the phone side triggers discovery, so you can either: - Just spam and see if you can see a connection on either side for a fraction of second - Check the phone with logcat which is likely most feasible to use through adb - Check the PC by (optionally?) killing kdeconnectd and running: QT_LOGGING_RULES="*.debug=true; qt.*.debug=false" /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd --replace I'm suspecting all these issues to be related even if the hotspot one is not clear, but even there the remarks of adding by IP address suggests that skipping the broadcast discovery phase is what fixes the issue. -- You are receiving this mail because: You are watching all bug changes.
