By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 1183 - KGPG not recognizing gpg-agent process
Summary: KGPG not recognizing gpg-agent process
Status: NEEDINFO
Alias: None
Product: TDE
Classification: Unclassified
Component: tdeutils (show other bugs)
Version: R14.0.x [Trinity]
Hardware: Other Linux
: P5 enhancement
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2012-08-24 15:13 CDT by Kris
Modified: 2019-02-22 14:28 CST (History)
4 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kris 2012-08-24 15:13:13 CDT 
I have gpg-agent running on my system. However, KGPG does not recognize that it is running. It displays the error:

----------------------------------
The use of [b]GnuPG Agent[/b] is enabled in GnuPG's configuration file (/home/{user}/.gnupg/gpg.conf).
However, the agent does not seem to be running. This could result in problems with signing/decryption.
Please disable GnuPG Agent from KGpg settings, or fix the agent.
----------------------------------

top shows gpg-agent as running. Also, I tried decrypting a file twice from the command line. The first time, I got the pinentry dialog asking for a password. The second time, it did not ask for the password, but was instead able to successfully decrypt using the cache'ed password (I have caching enabled in gpg-agent.conf).

Decrypting via KGPG seems to work -- right-clicking an encrypted file in Konqueror and opening it with KGPG brings up KGPG's password dialog (not pinentry as is set in gpg-agent.conf). A second test shows that KGPG is not honoring my caching settings in gpg-agent.conf.

I am using gpg2 version 2.0.14 on Debian Squeeze.

I'm not sure if this applies to other distros.
Comment 1 deloptes 2017-08-01 15:10:02 CDT 
How did you get gpg2 2.0.14 in squeeze - wasn't it before wheezy? And in lenny I had gpg 1.14

How is this reproducible when I can not reproduce? I took stretch now and created new user. I completed the Kgpg wizard. Logged out and logged in - still working.

in the shell

$ export | grep GPG
declare -x GPG_AGENT_INFO="/run/user/1000/gnupg/S.gpg-agent:0:1"

gpg --version

2.1.18

regards
Comment 2 Michele Calgaro 2018-07-29 04:29:40 CDT 
Kris, is this bug still valid?