https://bugs.kde.org/show_bug.cgi?id=424606
--- Comment #2 from asca...@q.com --- Previously, this bug was even more vexing than it otherwise would be because of the lack of any useful error messages in any of the logs. After the Neon update to Plasma 5.20, this changed. These are from the syslog on my laptop (named G3): kdeconnect.core: Disconnecting due to fatal SSL Error: "The issuer certificate of a locally looked up certificate could not be found" Oct 14 01:34:00 G3 kdeconnectd[1794]: kdeconnect.core: Disconnecting due to fatal SSL Error: "No certificates could be verified" Oct 14 01:34:00 G3 kdeconnectd[1794]: kdeconnect.core: Got connection for the same deviceId but certificates don't match. Ignoring "_12631ed7_e1ae_4485_8360_fe9814dae644_" SSL error, you say? With this new information, I went poking around and found that the distros that had working KDE Connect (such as Fedora 32) were using versions of OpenSSL other than 1.1.1f, the one in Neon (20.04). I did a quick search and found that OpenSSL 1.1.1h and LibSSL 1.1.1h were available in .deb form from the Debian Sid repo. I downloaded and installed both, and after pairing once more, KDE Connect works! The pairing does not disappear when I press "refresh," and I was able to send files in both directions (from the Neon 20.04 G3 to my desktop running Fedora 32, Plasma spin). -- You are receiving this mail because: You are watching all bug changes.
