Bug 359041

Summary:	kmail: gpg backend no longer working with error: "An error occurred while fetching the keys from the backend: General error"
Product:	[Fedora] Fedora	Reporter:	Douglas E. Warner <silfreed>
Component:	kdepim	Assignee:	Than Ngo <than>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	7	CC:	rdieter
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	F8	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-01-02 15:16:00 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Douglas E. Warner 2007-10-30 19:56:35 UTC

Description of problem:
When trying to configure KMail's gpg key settings, the following error dialog 
is shown:

An error occurred while fetching the keys from the backend:
General error

Additionally, the messages that I send that are "signed" don't appear to be 
signed with my key, despite the pinhelper popping up and asking for my 
passphrase.


Version-Release number of selected component (if applicable):
$ rpm -q kdepim
kdepim-3.5.7-10.svn20070926.ent.fc7


How reproducible:
always.


Steps to Reproduce:
1. In kmail, Settings->Configure KMail
2. Identities tab, modify a menu
3. if you have keys selected for this identity, you will get an error right 
away; otherwise, go to the cryptography tab and select 'change' for one of the 
keys.
  
Actual results:
The error described above.

Expected results:
Messages are signed correctly.

Additional info:
None.

Comment 1 Rex Dieter 2007-11-30 02:58:11 UTC

Can you try out this test build:
http://koji.fedoraproject.org/koji/buildinfo?buildID=26172

Comment 2 Douglas E. Warner 2007-11-30 15:58:04 UTC

Since upgrading to F8 I haven't experienced this bug.  I occasionally have 
problems where the gpg-agent isn't found, but typically restarting kmail fixes 
this.

Comment 3 Lukáš Tinkl 2008-01-02 15:16:00 UTC

Fixed in F8 according to reporter