kdeconnect's support for encrypted connections requires qca-ossl, and silently fails if qca-ossl is not present -- kdeconnect appears to run fine but the devices simply won't see each other. This applies to both versions of kdeconnect in the tree, 0.5.1 and 0.5.2.1. kdeconnect doesn't need to be rebuilt after qca-ossl is installed. Kudos to the kdeconnect test suite and https://qt-project.org/forums/viewthread/8574. emerge --info: Portage 2.2.8-r1 (hardened/linux/amd64, gcc-4.7.3, glibc-2.17, 3.13.6-hardened-r3 x86_64)
The source code has a message referring to qca-gnupg too, do you have any idea if that's required as well?
Ah, I see this now: core/daemon.cpp:73: if(!QCA::isSupported("rsa")) { core/daemon.cpp-74- //TODO: Maybe display this in a more visible way? core/daemon.cpp:75: kWarning(kdeconnect_kded()) << "Error: KDE Connect could not find support for RSA in your QCA installation, if your distribution provides" core/daemon.cpp:76: << "separate packages for QCA-ossl and QCA-gnupg plugins, make sure you have them installed and try again"; core/daemon.cpp-77- return; core/daemon.cpp-78- } I don't know the kdeconnect code at all, so I don't know what qca-gnupg would be used for. I tested all four combinations of having / not having qca-gnupg and qca-ossl installed, and pairing worked iff qca-ossl was installed, regardless of qca-gnupg. I only have qca-ossl now and multimedia controls, notifications, ping, file push work fine. Entirely possible it's needed for something I don't see though.
Thanks, fixed in CVS and git. I added only qca-ossl since there's no evidence that qca-gnupg is currently required. + 16 Jun 2014; Michael Palimaka <kensington@gentoo.org> kdeconnect-0.5.1.ebuild, + kdeconnect-0.5.2.1.ebuild: + Add missing dependency wrt bug #513372. http://git.overlays.gentoo.org/gitweb/?p=proj/kde.git;a=commit;h=feeceede3afdbda64e1c35a93ecdfb0310be401e
