Bug 435668

Summary: Since F33 kdeconnect can't find android devices
Product: [Applications] kdeconnect Reporter: BenderIRC <kdebugtracker>
Component: android-applicationAssignee: Albert Vaca Cintora <albertvaka>
Status: RESOLVED NOT A BUG    
Severity: normal    
Priority: NOR    
Version First Reported In: 1.6   
Target Milestone: ---   
Platform: Other   
OS: Other   
URL: https://bugzilla.redhat.com/show_bug.cgi?id=1946912
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description BenderIRC 2021-04-12 17:23:21 UTC 
Version-Release number of selected component:

Linux:   20.04.1-1        Fedora 33+ and others
Android: 1.14.2 + 1.16.0  AOS5


SUMMERY

Since an upgrade from F32 to F33, the F33 laptop can't find nor be found by any android device.

A pinephone running kdeconnect with rawhide can't be found either by the android device.

The rawhide pinephone and the F33 laptop can find and pair itself.

F32 Desktop pc with 20.04.1-1 can find F33 laptop with 20.04.1-1.

The Android 1.16.0 can find F32, but can't find F33+.

All firewalls are down: 

firewalld is inactive
iptables got flushed with -F


A tcpdump on f33 shows in fact connected tcp traffic between those two devices,
on the tcp port, but no sign of the other device.

Some dependency lib seems to cause this, as F32 and F33 are the same build version and behave differently. => KF5 Framework


NOTE:

A similar problem has been reported today on Pinephone Matrix international chat, by a, most likely, none Fedora user.
Comment 1 BenderIRC 2021-05-27 19:37:32 UTC 
Android: 1.17
 Fedora: 33

caused by SHA1 and TLS1.0 TLS1.1 being removed from the Fedora Crypto-Policy.

FIX:

Add SHA256 and TLS1.2 native to Android APP to circumvent the causing problem.

Workaround: 

update-crypto-policies --set DEFAULT:FEDORA32
killall kdeconnectd
Comment 2 BenderIRC 2024-07-31 17:32:44 UTC 
CLOSED