SUMMARY After upgrading to KDE Connect 25.03.90 the desktop app can no longer see my Android devices and the other way around (Android APP version 1.33.2 from Google Play store). STEPS TO REPRODUCE 1. Upgrade to 25.03.90 2. Reboot OBSERVED RESULT KJournald shows: kdeconnect.core: Invalid identity packet received kdeconnect.core: LanLinkProvider/newConnection: Host timed out without sending any identity. QHostAddress("::ffff:XXX") XXX= IPv4 of Android device Disabling firewalld completely didn't help EXPECTED RESULT KDE Connect still working (downgrading only the kdeconnect package 24.12.3 and restarting the service makes everything work again) SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 6.3.4 KDE Frameworks Version: 6.12.0 Qt Version: 6.9.0 Kernel Version: 6.14.0-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor Memory: 125.7 GiB of RAM Graphics Processor: AMD Radeon RX 7800 XT Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7D50 System Version: 1.0 ADDITIONAL INFORMATION
Same is happening to me, KSystemLog is showing the following everytime I refresh the devices list: 2025-04-06 16:30 kdeconnectd 2025-04-06T16:30:31 kdeconnect.core: Invalid identity packet received 2025-04-06 16:30 kdeconnectd 2025-04-06T16:30:32 kdeconnect.core: Invalid identity packet received 2025-04-06 16:30 kdeconnectd 2025-04-06T16:30:32 kdeconnect.core: LanLinkProvider/newConnection: Host timed out without sending any identity. QHostAddress("::ffff:192.168.0.25") 2025-04-06 1:30 kdeconnectd 2025-04-06T16:30:33 kdeconnect.core: LanLinkProvider/newConnection: Host timed out without sending any identity. QHostAddress("::ffff:192.168.0.25") SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.6 KDE Plasma Version: 6.3.4 KDE Frameworks Version: 6.12.0 Qt Version: 6.9.0 Kernel Version: 6.4.0-150600.23.42-default (64-bit) Graphics Platform: Wayland Smartphone KDE Connect version: FDroid 1.33.2 KDE Connect: 25.03.90 openSUSE Leap 15.6 (Wayland) KDE Frameworks: 6.12.0 Qt: Using 6.9.0 and built against 6.9.0 Build ABI: x86_64-little_endian-lp64 Kernel: linux 6.4.0-150600.23.42-default Interestingly, on NixOS nightly, using GNOME with GSConnect, I am able to connect to my phone. So, I think the issue lies with KDE Connect on Linux.
(In reply to Claudio from comment #0) > SUMMARY > After upgrading to KDE Connect 25.03.90 the desktop app can no longer see my > Android devices and the other way around (Android APP version 1.33.2 from > Google Play store). > > STEPS TO REPRODUCE > 1. Upgrade to 25.03.90 > 2. Reboot > > OBSERVED RESULT > KJournald shows: > > kdeconnect.core: Invalid identity packet received > kdeconnect.core: LanLinkProvider/newConnection: Host timed out without > sending any identity. QHostAddress("::ffff:XXX") > > XXX= IPv4 of Android device > Disabling firewalld completely didn't help > > EXPECTED RESULT > KDE Connect still working (downgrading only the kdeconnect package 24.12.3 > and restarting the service makes everything work again) > > SOFTWARE/OS VERSIONS > Operating System: EndeavourOS > KDE Plasma Version: 6.3.4 > KDE Frameworks Version: 6.12.0 > Qt Version: 6.9.0 > Kernel Version: 6.14.0-arch1-1 (64-bit) > Graphics Platform: Wayland > Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor > Memory: 125.7 GiB of RAM > Graphics Processor: AMD Radeon RX 7800 XT > Manufacturer: Micro-Star International Co., Ltd. > Product Name: MS-7D50 > System Version: 1.0 > > ADDITIONAL INFORMATION Hey! I have just found the solution!
Have added the bug report that helped me out, see above under "See Also:". There, the last comment reads: > there are two main reasons that can cause this -and related issues-: > - you are not running an updated desktop version 25.xx.xx (protocol mismatch) > - or you -initially- installed an android version older than 1.24.x (short > device-id) > > solutions: > - for the first, if you can't upgrade the desktop version, you must > downgrade the android version below 1.33.x, a protocol version change made > untrusted devices not visible. > - for the second, the device-id auto-generated by android is too short (< 32 > chars) and the newer protocol doesn't support it, you can check this by > looking up your device on ~/.config/kdeconnnect/trusted_devices, the section > name is your device-id. if this is the case you need to delete your app data > and pair again your device. after that you _might_ upgrade your android > version. > > > some of this info was taken from github.com/metallkopf/konnect For me, clearing storage and cache on KDE Connect on my cellphone fixed the issue.
*** This bug has been marked as a duplicate of bug 501635 ***
(In reply to Eliseu Amaro from comment #3) > Have added the bug report that helped me out, see above under "See Also:". > > There, the last comment reads: > > there are two main reasons that can cause this -and related issues-: > > - you are not running an updated desktop version 25.xx.xx (protocol mismatch) > > - or you -initially- installed an android version older than 1.24.x (short > > device-id) > > > > solutions: > > - for the first, if you can't upgrade the desktop version, you must > > downgrade the android version below 1.33.x, a protocol version change made > > untrusted devices not visible. > > - for the second, the device-id auto-generated by android is too short (< 32 > > chars) and the newer protocol doesn't support it, you can check this by > > looking up your device on ~/.config/kdeconnnect/trusted_devices, the section > > name is your device-id. if this is the case you need to delete your app data > > and pair again your device. after that you _might_ upgrade your android > > version. > > > > > > some of this info was taken from github.com/metallkopf/konnect > > For me, clearing storage and cache on KDE Connect on my cellphone fixed the > issue. Yep - clearing storage on the Android APP helped also for me - Thanks :)