From owner-freebsd-questions@FreeBSD.ORG Fri Dec 12 14:11:42 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4FF7DD88 for ; Fri, 12 Dec 2014 14:11:42 +0000 (UTC) Received: from mail.xtaz.uk (tao.xtaz.uk [IPv6:2001:8b0:202::10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 11D89DC7 for ; Fri, 12 Dec 2014 14:11:41 +0000 (UTC) Received: by mail.xtaz.uk (Postfix, from userid 1001) id D0810209AF15; Fri, 12 Dec 2014 14:11:37 +0000 (GMT) Date: Fri, 12 Dec 2014 14:11:37 +0000 From: Matt Smith To: User questions Subject: Re: KGpg unable to detect "gpg-agent" Message-ID: <20141212141137.GD52267@xtaz.uk> Mail-Followup-To: Matt Smith , User questions References: <20141212084712.4c3de69b@scorpio> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20141212084712.4c3de69b@scorpio> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2014 14:11:42 -0000 On Dec 12 08:47, Jerry wrote: >Fri, 12 Dec 2014 08:44:48 -0500 > >When attempting to use KGpg, I receive this error message: > >The use of GnuPG Agent is enabled in GnuPG's configuration file (/home/gerard/.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. > >The agent is running: > >gerard 37899 0.0 0.1 45412 3248 - Ss Sun08AM 0:06.36 gpg-agent > >What is the problem? I tried rebooting without success. > >-- >Jerry I had a similar problem with the mutt email client since the upgrade from 2.0.x to 2.1.x where it couldn't see that gpg-agent was running. I fixed this by adding a new environment variable in my .bashrc startup: export GPG_AGENT_INFO="$HOME/.gnupg/S.gpg-agent" This may help as it looks like a similar issue. -- Matt