Summary: | KDE Daemon Connect crashes | ||
---|---|---|---|
Product: | [Applications] kdeconnect | Reporter: | Martin Mirchev <mirchevmartin2203> |
Component: | common | Assignee: | Albert Vaca Cintora <albertvaka> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | bibliotekarz96, criguada, cwo.kde, fabian, lbeltrame, lyrixcaz, nicolas.fella, tbp001 |
Priority: | NOR | Keywords: | drkonqi |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Martin Mirchev
2021-06-18 06:57:36 UTC
nico@localhost:~> /usr/lib64/libexec/kdeconnectd Could not find support for RSA in your QCA installation kdeconnect.daemon: "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." kdeconnect.core: Private key from "/home/nico/.config/kdeconnect/privateKey.pem" is not valid kdeconnect.daemon: "KDE Connect" : "Could not store private key file: /home/nico/.config/kdeconnect/privateKey.pem" KCrash: Application 'kdeconnectd' crashing... KCrash: Attempting to start /usr/lib64/libexec/drkonqi I can reproduce this on OpenSUSE Tumbleweed. Sounds like a downstream problem Already fixed: https://bugzilla.opensuse.org/show_bug.cgi?id=1187457 Can confirm that installing qca-qt5 fixes it. Thanks Fabian and Christophe After installing qca-qt5 and restarting kdeconnectd I do not have anymore the message "Could not find support for RSA in your QCA installation", but I still have the "key not valid" message: kdeconnect.core: Private key from "/home/cristiano/.config/kdeconnect/privateKey.pem" is not valid kdeconnect.core: LanLinkProvider/newConnection: Host timed out without sending any identity. QHostAddress("::ffff:192.168.178.100") Here is the situation with my qca-related installed packages: ~> LANG=C zypper se qca Loading repository data... Reading installed packages... S | Name | Summary | Type ---+--------------------+-----------------------------------------------------------+-------- | libqca-qt5 | Qt Cryptographic Architecture 2 | package i | libqca-qt5-2 | QCA library | package | libqca-qt5-devel | Development files for the Qt Cryptographic Architecture 2 | package | libqca-qt5-plugins | Various plugins for the Qt Cryptographic Architecture 2 | package | libqca-qt6-2 | QCA library | package i+ | 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 *** Bug 438857 has been marked as a duplicate of this bug. *** *** Bug 438876 has been marked as a duplicate of this bug. *** *** Bug 438922 has been marked as a duplicate of this bug. *** No duplicates in three years, I think we can safely consider this actually fixed with that OpenSUSE change. |