KDE Connect failed to start

English Install/Boot/Login
1

I have Tumbleweed version 20210615 and since the upgrade I get after booting up every time the message “KDE Connect failed to start”. in the Notifications there is always the following text:
KDE Connect

Could not store private key file: /home/uli/.config/kdeconnect/privateKey.pem

KDE Connect failed to start
Could not find support for RSA in your QCA installation. If your distribution provides separate packets for QCA-ossl and QCA-gnupg, make sure you have them installed and try again.

The file /home/uli/.config/kdeconnect/privateKey.pem is empty (as the message says).

uli@linux-4skc:~/.config/kdeconnect> ls -l privateKey.pem 
-rw------- 1 uli users 0 Jun 19 09:08 privateKey.pem

I did a zypper se QCA with the following result":

**linux-4skc:~ #** zypper se QCA 
Retrieving repository 'openSUSE:Factory' metadata ...............................................................................[done] 
Building repository 'openSUSE:Factory' cache ....................................................................................[done] 
Retrieving repository 'packman' metadata ........................................................................................[done] 
Building repository 'packman' cache .............................................................................................[done] 
Retrieving repository 'openSUSE-Tumbleweed-Non-Oss' metadata ....................................................................[done] 
Building repository 'openSUSE-Tumbleweed-Non-Oss' cache .........................................................................[done] 
Retrieving repository 'openSUSE-Tumbleweed-Oss' metadata ........................................................................[done] 
Building repository 'openSUSE-Tumbleweed-Oss' cache .............................................................................[done] 
Loading repository data... 
Reading installed packages... 

S  | Name            | Summary                                                   | Type 
---+-----------------+-----------------------------------------------------------+-------- 
i+ | libqca-qt5-2    | QCA library                                               | package 
   | libqca-qt6-2    | QCA library                                               | package 
   | qca-qt5         | Qt Cryptographic Architecture 2                           | package 
   | qca-qt5-devel   | Development files for the Qt Cryptographic Architecture 2 | package 
i+ | qca-qt5-plugins | Various plugins for the Qt Cryptographic Architecture 2   | package 
   | qca-qt6         | Qt Cryptographic Architecture 2                           | package 
   | qca-qt6-devel   | Development files for the Qt Cryptographic Architecture 2 | package 
   | qca-qt6-plugins | Various plugins for the Qt Cryptographic Architecture 2   | package 
**linux-4skc:~ #** zypper se QCA-ossl 
Loading repository data... 
Reading installed packages... 
No matching items found. 
**linux-4skc:~ #** zypper se QCA-gnupg 
Loading repository data... 
Reading installed packages... 
No matching items found. 
**linux-4skc:~ #**

I use KDE Connect fairly often - how can I fix this?

2

There was an earlier thread on this.

For me, updating to 20210616 has fixed the problem.

3

OK - problem solved. I saw that qca-qt5 library the the qca-qt5 plugins are installed but not qca-qt5 itself. So I installed this then deleted the folder ~/.config/kdeconnect. After logout and login KDE Connect works again. Thanks nrickert, I only saw your thread after the reboot when KDE connect worked again.

4

Since the Monday updates my KDE connect cannot connect any more. The Phone still can connect to another PC. Also since monday Steam could not connect any more, only after restart into ubuntu, where it rebuilt keys, than restart into tumbleweed again rebuilind keys, Steam worked again. Also not working wine wechat cannot connect anymore. just ran all updates today, nothing changed so far.

5

resolved my issue
by deleting

/home/USER/.config/kdeconnect

then killing the processes:

kdeconnectd
kdeconnect-settings

and then it works again. So it is a key issue.