From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marco van Hulten Subject: Re: gpg-agent error: No pinentry Date: Fri, 20 Dec 2019 22:15:14 +0100 Message-ID: <20191220221514.65fca628@jasniac.instanton> References: <20191218224127.5192dde2@jasniac.instanton> <20191218215008.GA8426@jurong> <20191219092258.30cccce4@jasniac.instanton> <20191219100240.3b404ba9@jasniac.instanton> <20191220104927.1533364a@gfi063209.klientdrift.uib.no> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:39724) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iiPcK-00043b-DI for help-guix@gnu.org; Fri, 20 Dec 2019 16:15:25 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iiPcJ-0004JJ-6J for help-guix@gnu.org; Fri, 20 Dec 2019 16:15:24 -0500 Received: from alfons.uib.no ([2001:700:200:30::141]:53057) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iiPcI-0003s7-54 for help-guix@gnu.org; Fri, 20 Dec 2019 16:15:23 -0500 In-Reply-To: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: =?UTF-8?B?R8OhYm9y?= Boskovits Cc: help-guix G=C3=A1bor=E2=80=94 Thank you for the help: the issue might have been solved, at least sometimes (sort-of explanation follows)! Je 20 dec 20:12 skribis G=C3=A1bor: > If you still have the patience to experiment a little could you try > with pinentry-tty on the console and pinentry-gtk on a gui? Yes, I just had a little bit of time before the new year. (Christmas is a holiday, they say!) > It might be a valuable experience, and a feedback that our simple > pinentry is faulty in some ways. >=20 > I have extracted the inforamtions from my config, and it looks like this: >=20 > manifest: (specifications->manifest '("gnupg" "pinentry-tty")) >=20 > I also use guix home-manager [...] A guix home-manager sounds intriguing. I alluded to it once when asking why we wouldn't define the state of the whole computing environment. But it adds a layer of complexity and so I don't think it would be very useful to use this to analyse the problem I'm having. > I am using bash, and I also have: >=20 > At the end of my .bashrc: > export GPG_TTY=3D$(tty) >=20 > And at the end of my .bash_profile: >=20 > gpg-agent --options /home/gabriel/.home-config/.gnupg/gpg-agent.conf --da= emon >=20 > I believe that is all. >=20 > Could you have a look if it works for you with these settings? Also, > please not that these are for console only use, most probably some > other tweaks are needed to use this form a gui. Yes, this helps! That is, when I set GPG_TTY and started the gpg-agent like this, 'gpg --import' and 'gpg -d' started to work without complaining about pinentry. But then I tried the same as another user and there it still complained. So I went back to the first user again, removed the GPG_TTY variable and killed the gpg-agent, but now it does not complain anymore about pinentry anymore at all. I don't understand what's going on, but for now I'll just add the export and gpg-agent commands in my .bashrc since that seemed to do the trick at least once. export GPG_TTY=3D$(tty) gpg-agent --options ${HOME}/.gnupg/gpg-agent.conf --daemon =E2=80=94Marco