Eric Valette ha scritto:
I keep reading wonderful things about KDEconnect but I've yet to experience
them. My android phones can't see my Debian/Buster desktop and vice versa.
Both devices are on the same network and I'm not running an internal
firewall on my desktop. I've been trying KDEconnect intermittently for many
months, during which time I've had a couple different Android phones, but
have yet to have any success. I have no indication of any other network
issues on my home network. Both IP addresses (phone & desktop) are assigned
via DHCP, which is probably about as normal as you can get. Manually adding
the desktop's current IP address to the phone app doesn't help either.
Any ideas?
I already reported this bug
<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898320>, even upstream
*<https://bugs.kde.org/show_bug.cgi?id=394646
<https://bugs.kde.org/show_bug.cgi?id=394646>*>, even on the kdeconnect dev
mailing list. Nobody answered. Its has been so for month.
Most likely it's not reproducible for the developers.
Using wireshark I see packet exchanged netween android devices and PCÂ but
probably the layout of the data are broken during network conversion when
exchanged (arm 32 bits and amd64 64 bits) .
If it was the case, it would have been broken for everyone. But for example it
works for me (and other people). So it can't simply be a matter of packages
mangled between different architectures.
You mention that you see packages, but do you see the specific packages for
kdeconnect? I don't see the firewall mentioned in the bug, I guess it was
disabled, but just to be sure... (even if probably Debian does not enable it
by default).
--
Luigi
