From debbugs-submit-bounces@debbugs.gnu.org Fri Jan 20 07:16:37 2017 Received: (at 25328) by debbugs.gnu.org; 20 Jan 2017 12:16:37 +0000 Received: from localhost ([127.0.0.1]:36071 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cUY7Q-0001ZZ-OV for submit@debbugs.gnu.org; Fri, 20 Jan 2017 07:16:36 -0500 Received: from relay4-d.mail.gandi.net ([217.70.183.196]:50132) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cUY7P-0001ZP-Fh for 25328@debbugs.gnu.org; Fri, 20 Jan 2017 07:16:35 -0500 Received: from mfilter35-d.gandi.net (mfilter35-d.gandi.net [217.70.178.166]) by relay4-d.mail.gandi.net (Postfix) with ESMTP id 826131720B1; Fri, 20 Jan 2017 13:16:33 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at mfilter35-d.gandi.net Received: from relay4-d.mail.gandi.net ([IPv6:::ffff:217.70.183.196]) by mfilter35-d.gandi.net (mfilter35-d.gandi.net [::ffff:10.0.15.180]) (amavisd-new, port 10024) with ESMTP id 1aJ8fBbdNds4; Fri, 20 Jan 2017 13:16:32 +0100 (CET) X-Originating-IP: 10.58.1.147 Received: from webmail.eu.com (webmail7-d.mgt.gandi.net [10.58.1.147]) (Authenticated sender: d4n1@d4n1.org) by relay4-d.mail.gandi.net (Postfix) with ESMTPA id 9CB991720C3; Fri, 20 Jan 2017 13:16:31 +0100 (CET) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Fri, 20 Jan 2017 09:16:31 -0300 From: Daniel Pimentel To: Chris Marusich Subject: Re: bug#25328: gpg: "Operation cancelled" with pinentry 1.0.0 on GNOME In-Reply-To: <87wpdqdu7k.fsf@gmail.com> References: <87a8ba44d5.fsf@gmail.com> <877f64r3qg.fsf@gnu.org> <87wpdqdu7k.fsf@gmail.com> Message-ID: X-Sender: d4n1@d4n1.org User-Agent: Roundcube Webmail/1.1.2 X-Spam-Score: -0.7 (/) X-Debbugs-Envelope-To: 25328 Cc: bug-Guix , ludo@gnu.org, 25328@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -0.7 (/) I used this: gpg-agent --daemon --use-standard-socket --pinentry-program /home/dani/.guix-profile/bin/pinentry-curses It's works for me. More in my site: https://d4n1.org/gnupg.html Thanks, --- Daniel Pimentel (d4n1) On 2017-01-20 05:14, Chris Marusich wrote: > Hi, > > Previously, I wrote: > >> In GNOME, this issue DOES occur regardless of which "pinentry" program >> I specify in my ~/.gnupg/gpg-agent.conf file (the same issue occurs >> with pinentry, pinentry-curses, pinentry-gtk-2, and pinentry-tty). > > I don't think this is actually true. I believe I made an error when > testing the different pinentry programs. I believe I forgot to restart > the gpg-agent, which would explain why simply changing the contents of > the gpg-agent.conf file did not seem to fix the issue. > > I did another test just now. I tried changing the contents of the > gpg-agent.conf file, and I made sure to kill the gpg-agent process > after > each change, so that gpg-agent would reload the file for sure. When I > did this, I found that only pinentry-gtk-2 exhibits this issue (note > that pinentry is a symlink to pinentry-gtk-2). In particular, > pinentry-curses, pinentry-tty, and pinentry-gnome3 all worked for me. > > Is anyone able to reproduce the issue using pinentry-gtk-2? The > following steps should reproduce the issue: > > * Log into a GNOME session on (a recently updated) GuixSD. > > * In $HOME/.gnupg/gpg-agent.conf, set pinentry-program to > pinentry-gtk-2, for example: > > pinentry-program /home/marusich/.guix-profile/bin/pinentry-gtk-2 > > * If the gpg-agent process is running, kill it to make sure it loads > the > new gpg-agent.conf. > > * Try to sign a message, e.g.: > > echo hello > /tmp/message > gpg --sign /tmp/message > > You should get the error very frequently. > > ludo@gnu.org (Ludovic Courtès) writes: > >> For the record, I’ve never experienced this problem (that’s outside of >> GNOME) with: > > For me, this problem doesn't happen outside of GNOME. > >> $ guix package -I '(gnupg|pinentry)' >> pinentry 1.0.0 out /gnu/store/57dg2i4backl38bw4ipcsdg1b7df9j64-pinentry-1.0.0 >> gnupg 2.1.16 out /gnu/store/fz44xcp1iksikjvcc472bgsr9hs8ygkq-gnupg-2.1.16 > > I'm using these versions: > > $ guix package -I '(gnupg|pinentry)' > > gnupg 2.1.17 out /gnu/store/mcsi9rp06q0xxds4mwdgh1p16bifjxvk-gnupg-2.1.17 > > pinentry-gnome3 1.0.0 out /gnu/store/4kq8isyz7k8y64l7mjy90y4rjv7mh9x8-pinentry-gnome3-1.0.0 > > > The problem also occurred when using the "pinentry" package (instead of > the "pinentry-gnome3" package): > > /gnu/store/b72r4rgr9irqy5zvb8i9hmrgrbb88ndf-pinentry-1.0.0 > >> ISTR that GNOME has a hack to force its own Pinentry tool. Could it >> be >> what’s at fault? > > Where can I find more info about this hack? I did some Internet > searches, but I couldn't find anything specific. > > This bug is no longer blocking me, since I can use pinentry-gnome3, but > I'm still concerned about the fact that pinentry-gtk-2 fails very > frequently, even though it didn't on the previous version.