Bug 366154

Summary:	GPG Settings cannot be configured any more
Product:	[Applications] kaddressbook	Reporter:	Stephan Mueller <smueller>
Component:	general	Assignee:	kdepim bugs <pim-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	montel, tokoe
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Stephan Mueller 2016-07-27 06:56:09 UTC

Version: 16.04.3

With the switch to Fedora 24 (which uses KDEPIM 5 for the first time), the kaddressbook does not allow configuring the GPG / SMIME settings any more. Kmail still honors X-KADDRESSBOOK-OPENPGPFP but yet there is no frontend any more to manipulate them.

Please resurrect the possibility to configure the crypto settings as this is the only way to define GPG groups (the group setting in gpg.conf is not usable as it is not exported by libgpgme).

Reproducible: Always

Comment 1 Laurent Montel 2016-07-27 07:16:32 UTC

install kdepim-addons

Comment 2 Stephan Mueller 2016-07-27 07:23:59 UTC

kdepim-addons is installed -- is there a lib missing from the F24 RPM?

$ rpm -ql kdepim-addons | grep kaddress
/usr/lib64/libkaddressbookmergelibprivate.so.5
/usr/lib64/libkaddressbookmergelibprivate.so.5.2.3
/usr/lib64/qt5/plugins/kaddressbook
/usr/lib64/qt5/plugins/kaddressbook/kaddressbook_checkgravatarplugin.so
/usr/lib64/qt5/plugins/kaddressbook/kaddressbook_mergecontactsplugin.so
/usr/lib64/qt5/plugins/kaddressbook/kaddressbook_searchduplicatesplugin.so
/usr/lib64/qt5/plugins/kaddressbook/kaddressbook_sendmailplugin.so
/usr/lib64/qt5/plugins/kaddressbook/kaddressbook_sendvcardsplugin.so

Comment 3 Laurent Montel 2016-07-27 11:48:02 UTC

did you have ./akonadi/contact/editorpageplugins/cryptopageplugin.so ?

Comment 4 Stephan Mueller 2016-07-27 11:53:05 UTC

Yes:

/usr/lib64/akonadi/contact/editorpageplugins/cryptopageplugin.so

$ rpm -qf /usr/lib64/akonadi/contact/editorpageplugins/cryptopageplugin.so
kdepim-addons-16.04.3-1.fc24.x86_64

Comment 5 Laurent Montel 2016-08-03 15:36:54 UTC

it was a fedora rpm bug.
I discussed with fedora maintainer and he fixed it.