Version: 1.9.1 (using KDE 3.5.2, compiled sources) Compiler: gcc version 3.4.4 [FreeBSD] 20050518 OS: FreeBSD (i386) release 6.1-STABLE The following happens in KMail on a regular basis. When I first attempt to send a signed message, I am asked for my password phase. That works as it should. If I send another message within a short period of time, I am not bothered for the password since I have gpg-agent running. Now, if I wait more than approximately one-half hour, and attempt to send another signed message, I am greeted with a message telling me that gpg-agent was found but not running. That is not correct. This is the out put of ps | grep for gpg-agent: ~ # ps | grep "gpg-agent" root 46228 0.0 0.3 3248 1112 ?? Ss 4:29PM 0:00.63 gpg-agent --daemon --use-standard-socket I will be attaching a snap shot of the screen error message with this bug report. I have configured gpg-agent's expire cache PIN's after n seconds to 604800 which should preclude it timing out in less than one hour, but it doesn't.
Created attachment 16519 [details] Screen shot of error message This is the error message that gets displayed.
AFAIK gnupg uses gpg-agent transparently and calls the password callback function in the application in case gpg-agent was not found (i.e. it's only a fallback option). In that case this would be a gnupg bug and not a kmail one. I'd like somebody with more knowledge to comment on this though :)
When KMail says gpg-agent cannot be found, try signing something using gpg from the command-line. If it asks for your password in the terminal, gpg-agent cannot be found by anything, so it's not a KMail bug.
Thank you for taking the time to file a bug report. KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2. We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback.