Bug 460495 - When ever I try to connect my Linux mint laptop with my android phone, it shows that "error trying to pair: this device cannot be paired because it is running an old version of KDE connect. But I am using the latest kde connect app available in Play Store
Summary: When ever I try to connect my Linux mint laptop with my android phone, it sho...
Status: NEEDSINFO WAITINGFORINFO
Alias: None
Product: kdeconnect
Classification: Applications
Component: android-application (other bugs)
Version First Reported In: unspecified
Platform: Mint (Ubuntu based) Linux
: NOR normal
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-10-15 17:57 UTC by Nandu
Modified: 2026-02-12 03:58 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
This is the error I am getting. (1.64 MB, image/jpeg)
2022-10-15 18:02 UTC, Nandu 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Nandu 2022-10-15 17:57:19 UTC 
STEPS TO REPRODUCE
1. Open "Configure-KDE connect settings" and click on the device you want to pair. 
2. Click "Request pair"
3. And the error shows up

OBSERVED RESULT
A dialog box saying that "error trying to pair: this device cannot be paired because it is running an old version of KDE connect"

EXPECTED RESULT
I expected it to pair with my phone.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Linux Mint 21
(available in About System)
KDE Plasma Version: 5.24.6
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION
I am trying to pair an Linux laptop and Android 10 smart phone.
Comment 1 Nandu 2022-10-15 18:02:27 UTC 
Created attachment 152856 [details]
This is the error I am getting.
Comment 2 sunny 2022-11-15 17:43:39 UTC 
Same here. Ubuntu 22.10 with KDE Connect 22.08.3 on my desktop; Android 13 with KDE Connect 1.19.1 on my phone.

Console output of kdeconnectd:
qt.network.ssl: QSslSocket: cannot resolve SSL_get1_peer_certificate
qt.network.ssl: QSslSocket: cannot resolve EVP_PKEY_get_base_id
qt.network.ssl: QSslSocket: cannot resolve SSL_CTX_load_verify_dir
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_CTX_load_verify_dir
qt.network.ssl: An error encountered while to set root certificates location: ""
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_get1_peer_certificate
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_get1_peer_certificate
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_CTX_load_verify_dir
qt.network.ssl: An error encountered while to set root certificates location: ""
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_get1_peer_certificate
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_get1_peer_certificate
qt.network.ssl: QSslSocket: cannot call unresolved function EVP_PKEY_get_base_id
Device pairing error "This device cannot be paired because it is running an old version of KDE Connect."
Comment 3 Minabsapi 2023-01-14 23:30:32 UTC 
Same issue. I've seen from a rapid check at journalctl similar entries to what Eric Rösch reported

I noticed the common factor is that we're using Ubuntu 22.xx in a way or another. A quick search about one of the logs led me to another repository issue where the solution was to patch OpenSSL. So it might be linked to the OpenSSL version bundled in this distribution version

Desktop OS: Linux Mint 21.1
Mobile OS: Android 8.1
KDE Connect (desktop client) version: 22.04.3
KDE Connect (mobile client) version: 1.21.1
Comment 4 aristsakas 2026-01-27 10:47:35 UTC 
Thank you for the bug report. Unfortunately we were not able to get to it yet. Can we ask you to please check if this is still an issue with KDE Connect 25.12.
Comment 5 cwo 2026-01-28 21:14:18 UTC 
.
Comment 6 Bug Janitor Service 2026-02-12 03:58:24 UTC 
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!