Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 453406 - GPG backend is unavailable due to general error in kontact but not kmail
Summary: GPG backend is unavailable due to general error in kontact but not kmail
Alias: None
Product: Fedora
Classification: Fedora
Component: kdepim
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Ngo Than
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2008-06-30 13:07 UTC by Douglas E. Warner
Modified: 2008-08-27 13:50 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-08-27 13:50:16 UTC

Attachments (Terms of Use)

Description Douglas E. Warner 2008-06-30 13:07:36 UTC
Description of problem:
When using kontact, I get the following error when trying to edit my GPG key in
my identity:
"An error occurred while fetching the keys from the backend:
General error"

I can immediately exist kontact and load kmail and can manage my identity
(including GPG keys) as well as sign messages normally.

Version-Release number of selected component (if applicable):
(from kde-redhat, also occured with rawhide versions)

How reproducible:
Sometimes shortly after I've logged in I can use kontact to send a signed email,
but it doesn't seem to last long.  I have confirmed that gpg-agent is still
running and the environment variable is set properly.

Additional info:
My first guess is that maybe kontact isn't passing the GPG_AGENT_INFO
environment variable on to the kmail kpart properly, but I really have no idea.

Comment 1 Steven M. Parrish 2008-07-17 19:57:38 UTC
Checked upstream and did not find a matching report.  Please file upstream at and add upstream info to this report.  Thanks

Comment 2 Steven M. Parrish 2008-08-27 13:50:16 UTC
The information we've requested above is required in order
to review this problem report further and diagnose or fix the
issue if it is still present.  Since it has been thirty days or
more since we first requested additional information, we're assuming
the problem is either no longer present in the current Fedora release, or
that there is no longer any interest in tracking the problem.

Setting status to "CLOSED INSUFFICIENT_DATA".  If you still
experience this problem after updating to our latest Fedora
release and can provide the information previously requested,
please feel free to reopen the bug report.

Thank you in advance.

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