Bug 359041 - kmail: gpg backend no longer working with error: "An error occurred while fetching the keys from the backend: General error"
Summary: kmail: gpg backend no longer working with error: "An error occurred while fet...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kdepim
Version: 7
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-10-30 19:56 UTC by Douglas E. Warner
Modified: 2008-01-02 15:16 UTC (History)
1 user (show)

Fixed In Version: F8
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-01-02 15:16:00 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

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


Note You need to log in before you can comment on or make changes to this bug.