From unknown Fri Jun 13 09:59:43 2025 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Mailer: MIME-tools 5.509 (Entity 5.509) Content-Type: text/plain; charset=utf-8 From: bug#25328 <25328@debbugs.gnu.org> To: bug#25328 <25328@debbugs.gnu.org> Subject: Status: gpg: "Operation cancelled" with pinentry 1.0.0 on GNOME Reply-To: bug#25328 <25328@debbugs.gnu.org> Date: Fri, 13 Jun 2025 16:59:43 +0000 retitle 25328 gpg: "Operation cancelled" with pinentry 1.0.0 on GNOME reassign 25328 guix submitter 25328 Chris Marusich severity 25328 normal tag 25328 unreproducible thanks From debbugs-submit-bounces@debbugs.gnu.org Sun Jan 01 20:50:51 2017 Received: (at submit) by debbugs.gnu.org; 2 Jan 2017 01:50:51 +0000 Received: from localhost ([127.0.0.1]:38930 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cNrlz-0000gN-J3 for submit@debbugs.gnu.org; Sun, 01 Jan 2017 20:50:51 -0500 Received: from eggs.gnu.org ([208.118.235.92]:41067) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cNrlx-0000g7-8z for submit@debbugs.gnu.org; Sun, 01 Jan 2017 20:50:50 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cNrlr-00048s-01 for submit@debbugs.gnu.org; Sun, 01 Jan 2017 20:50:44 -0500 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on eggs.gnu.org X-Spam-Level: X-Spam-Status: No, score=0.8 required=5.0 tests=BAYES_50,FREEMAIL_FROM, T_DKIM_INVALID autolearn=disabled version=3.3.2 Received: from lists.gnu.org ([2001:4830:134:3::11]:49380) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cNrlq-00048f-OY for submit@debbugs.gnu.org; Sun, 01 Jan 2017 20:50:42 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60271) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cNrlp-00085u-CN for bug-guix@gnu.org; Sun, 01 Jan 2017 20:50:42 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cNrlo-00047p-FO for bug-guix@gnu.org; Sun, 01 Jan 2017 20:50:41 -0500 Received: from mail-pg0-x231.google.com ([2607:f8b0:400e:c05::231]:34768) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cNrlo-00047b-7x for bug-guix@gnu.org; Sun, 01 Jan 2017 20:50:40 -0500 Received: by mail-pg0-x231.google.com with SMTP id y62so146777313pgy.1 for ; Sun, 01 Jan 2017 17:50:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:user-agent:mime-version; bh=9+OTxIuPkJLReKx/7UuB2dmCfJp6NOwC1CL03Aa4/mo=; b=cgyTdq/OZMRqqOO2hikTnOB17E/P6fwXdiT+qthg9I3/wv1PYTRuuVAjo5i2Tgh8wN MNuSO0GEIogNxFIy5urXvUpg0ANdJ8z4jXX8JkNu5HT4S99XKmguJTKUy3rJpe3JWLeY chfVjeRTNBaSpFAsJSXHxa6rc4FLW06/q0kAgdKam1W9/rgFrDZcdg9v0Ssh5z/ixgdL RWCh95h3Itv4RACrEjquve2kot3ta0BcRk0Lv+ev1zwV0N9CTwIn37VjSF2KOCDKQdc1 sAiBdqKOY9bX4zqs98BbXflERV+KZr2O0CVb8qGhiF7k+9O2yQEHtt/j7mTYTS7tT2cV 56Qw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:user-agent :mime-version; bh=9+OTxIuPkJLReKx/7UuB2dmCfJp6NOwC1CL03Aa4/mo=; b=NmDJT/j0EUkVdPWvSaKapP3vXcccfkr9q+V2Nrc5+mz5Z6SnxGacCJAJnS/to9SUc4 oSwoWkPHEVl8oMtwbuhohchRT63JbK8sBXOboEzfsKsad82g5qQjZtcfp50bqTITrz6B OlOeNQEgk/NTBFTsNQWMCIM8Ua6AeWuKDx4uxSwD1NMwvHk9wzK97pzqoTjfVOyWTQDC /VtECeO5hEDoF0DUD5IKt3kbfWPVCa8aVrgVkV2P03JijNE39xcaddRHPyiXkRnpqlVV rJDGrOemIzyZozLnCHdG/G7dq+vUmirglIEVefX3q5MVFYySLh4fr+gueu1M7JNe1W5M S33Q== X-Gm-Message-State: AIkVDXLQpomNPR9GVMYXLLzo9vQivQTU4A0dAyZ7DWm7np8Uv04L3tNJWIhsjCuNlqxoiA== X-Received: by 10.98.201.199 with SMTP id l68mr40604379pfk.154.1483321839030; Sun, 01 Jan 2017 17:50:39 -0800 (PST) Received: from garuda ([2601:602:9d02:4725:4e0f:6eff:fef6:70b9]) by smtp.gmail.com with ESMTPSA id m69sm69915772pfj.34.2017.01.01.17.50.37 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 01 Jan 2017 17:50:38 -0800 (PST) From: Chris Marusich To: bug-guix@gnu.org Subject: gpg: "Operation cancelled" with pinentry 1.0.0 on GNOME Date: Sun, 01 Jan 2017 17:50:30 -0800 Message-ID: <87a8ba44d5.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 2001:4830:134:3::11 X-Spam-Score: -4.0 (----) X-Debbugs-Envelope-To: submit Cc: Leo Famulari 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: -4.0 (----) --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi, Since upgrading pinentry from 0.9.7 to 1.0.0, I've noticed some strange behavior. In GNOME only, when gpg tries to access my secret key, the attempt fails without prompting me for my passphrase. For example, it fails like this: =2D-8<---------------cut here---------------start------------->8--- [0] marusich@garuda:~ $ echo hello > /tmp/message [0] marusich@garuda:~ $ gpg --sign /tmp/message=20 gpg: signing failed: Operation cancelled gpg: signing failed: Operation cancelled [2] marusich@garuda:~ $=20 =2D-8<---------------cut here---------------end--------------->8--- No prompt appears, GUI or otherwise. However, if I repeat the "gpg =2D-sign" command many times, eventually a GUI does appear which asks me for a password. In that case, everything works just fine. But about 90-95% of the time, the attempt just fails like above, without showing me any prompt. This problem is not limited to my manual command-line invocation. The same kind of issue also occurs when emacs (the graphical version, running in GNOME) tries to automatically decrypt encrypted files (e.g., when gnus needs to read my ~/.authinfo.gpg file to connect to an email server). Normally, when emacs needs to decrypt a file like this, a new window pops up to ask me for my passphrase, but because of this issue, the decryption fails, without showing me a prompt, for a similar reason: =2D-8<---------------cut here---------------start------------->8--- Error while decrypting with "gpg": gpg: encrypted with 4096-bit RSA key, ID 0FE3DE4943560F06, created 2016-02-= 19 "Chris Marusich " gpg: public key decryption failed: Operation cancelled gpg: decryption failed: No secret key =2D-8<---------------cut here---------------end--------------->8--- I suspect these are symptoms of the same issue. My ~/.gnupg/gpg-agent.conf contains the following single line: pinentry-program /home/marusich/.guix-profile/bin/pinentry This issue does NOT occur in Xfce. This issue does NOT occur when I run the "gpg --sign" command in a virtual terminal (e.g., by pressing Control+Alt+F2 to switch to a virtual terminal). 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've run both "guix pull" and "sudo guix pull" successfully in the last few days, and I've successfully reconfigured my system since then, so I'm using the most recent Guix software. I'm using GuixSD. Since I've added and modified many things to my home directory, I tried creating a test user with a fresh home directory to rule out my local customizations as a cause. I was able to reproduce the issue using a fresh test user in GNOME after installing gnupg and pinentry via "guix package -i gnupg pinentry". The only changes I made to the test user's home directory were (1) I added the "export" statements to its ~/.bashrc file which were suggested by Guix after installing those two packages, and (2) I added a ~/.gnupg/gpg-agent.conf which uses the pinentry that got installed into the test user's profile. So, I expect that other users of GuixSD can probably reproduce this issue. =2D-=20 Chris --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEy/WXVcvn5+/vGD+x3UCaFdgiRp0FAlhpseYACgkQ3UCaFdgi Rp0m8RAAjmswfheDR01c7OpH1YjFdgj4jVZdx+s171hVGrJ71iDYbIUJIlhgyXHY yPt8XJJ2p2GZzYGCDUcFBFy9endNC+tw1jTVSRtjprP3Fc5PjOeene9vZDFmKiwD SckWSRcGq4xOgF4SGuTwad13TdasVmcBcOqZ1GyfJINwpDL59yCMgO5fQ+M/j/9e JSKW4RQqqZFJyVarbSQWTEEKm4h8RXx1ewJLtS9EbLlzXxd+lN4uRo7KK+2Xh6fN us5tzJnM0tawo4/x2PL+2ryS18wsNf1x6bNf2SJ1WoX7KmO4b4wfl0FCOUsq7Ey1 sdk0kMqRGCd8LClEULI/jt9Nc3DJ9vuvoSA5IBPyJbxdf3QyzxTm9LN7Kqf2uG5+ nItJTnmk7jVwWaxggQMFlM0t0lkAmhODGuCdBqS7TWgASg9Q47NtX41QTTHmiPOM r2eWkDGAT37JdHmIMreXel7uiF3ePZed/XvRa9XtOCXSlN8Wqep2FuZ3LuBFAk46 MUWCt3sk4S3SmOL1nGbf+47Ghk3HxSFA6P1tSDch+L81UvbHbbbEkMm40pCqkacg Xq6XwDY38VpyfTa77DlTigvqNBuxRHlQRcFE2AeH0VXjRMQniuJk5T/4CTrlLlUU P8dq9gcIFtbD5GcrUsIRv2M6uhqj7yEKGymvUY5l6I4Gx5J84Yo= =7tms -----END PGP SIGNATURE----- --=-=-=-- From debbugs-submit-bounces@debbugs.gnu.org Mon Jan 09 04:18:28 2017 Received: (at 25328) by debbugs.gnu.org; 9 Jan 2017 09:18:28 +0000 Received: from localhost ([127.0.0.1]:47383 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cQW60-0001gP-5V for submit@debbugs.gnu.org; Mon, 09 Jan 2017 04:18:28 -0500 Received: from eggs.gnu.org ([208.118.235.92]:34073) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cQW5z-0001gD-0U for 25328@debbugs.gnu.org; Mon, 09 Jan 2017 04:18:27 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cQW5q-0002b6-PU for 25328@debbugs.gnu.org; Mon, 09 Jan 2017 04:18:21 -0500 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on eggs.gnu.org X-Spam-Level: X-Spam-Status: No, score=-3.2 required=5.0 tests=BAYES_40,RP_MATCHES_RCVD autolearn=disabled version=3.3.2 Received: from fencepost.gnu.org ([2001:4830:134:3::e]:40641) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cQW5q-0002b2-Ln; Mon, 09 Jan 2017 04:18:18 -0500 Received: from [193.50.110.224] (port=43738 helo=ribbon) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1cQW5q-0004jQ-3N; Mon, 09 Jan 2017 04:18:18 -0500 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) To: Chris Marusich Subject: Re: bug#25328: gpg: "Operation cancelled" with pinentry 1.0.0 on GNOME References: <87a8ba44d5.fsf@gmail.com> X-URL: http://www.fdn.fr/~lcourtes/ X-Revolutionary-Date: 20 =?utf-8?Q?Niv=C3=B4se?= an 225 de la =?utf-8?Q?R?= =?utf-8?Q?=C3=A9volution?= X-PGP-Key-ID: 0x090B11993D9AEBB5 X-PGP-Key: http://www.fdn.fr/~lcourtes/ludovic.asc X-PGP-Fingerprint: 3CE4 6455 8A84 FDC6 9DB4 0CFB 090B 1199 3D9A EBB5 X-OS: x86_64-unknown-linux-gnu Date: Mon, 09 Jan 2017 10:18:15 +0100 In-Reply-To: <87a8ba44d5.fsf@gmail.com> (Chris Marusich's message of "Sun, 01 Jan 2017 17:50:30 -0800") Message-ID: <877f64r3qg.fsf@gnu.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-Spam-Score: -8.2 (--------) X-Debbugs-Envelope-To: 25328 Cc: 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: -8.2 (--------) Hi Chris, Chris Marusich skribis: > Since upgrading pinentry from 0.9.7 to 1.0.0, I've noticed some strange > behavior. In GNOME only, when gpg tries to access my secret key, the > attempt fails without prompting me for my passphrase. For example, it > fails like this: > > [0] marusich@garuda:~ > $ echo hello > /tmp/message > [0] marusich@garuda:~ > $ gpg --sign /tmp/message=20 > gpg: signing failed: Operation cancelled > gpg: signing failed: Operation cancelled > [2] marusich@garuda:~ > $=20 For the record, I=E2=80=99ve never experienced this problem (that=E2=80=99s= outside of GNOME) with: --8<---------------cut here---------------start------------->8--- $ 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 --8<---------------cut here---------------end--------------->8--- ISTR that GNOME has a hack to force its own Pinentry tool. Could it be what=E2=80=99s at fault? Thanks, Ludo=E2=80=99. From debbugs-submit-bounces@debbugs.gnu.org Fri Jan 20 03:14:20 2017 Received: (at 25328) by debbugs.gnu.org; 20 Jan 2017 08:14:20 +0000 Received: from localhost ([127.0.0.1]:36018 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cUUKy-0004G2-Di for submit@debbugs.gnu.org; Fri, 20 Jan 2017 03:14:20 -0500 Received: from mail-pf0-f170.google.com ([209.85.192.170]:34526) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cUUKx-0004Fp-1G for 25328@debbugs.gnu.org; Fri, 20 Jan 2017 03:14:19 -0500 Received: by mail-pf0-f170.google.com with SMTP id e4so20749144pfg.1 for <25328@debbugs.gnu.org>; Fri, 20 Jan 2017 00:14:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:in-reply-to:references:user-agent:date :message-id:mime-version; bh=KlrSrEH3su+rQAAod9kDXqltooHkhuPda7kM3VfUrI0=; b=bvMjkEnO0gCMN253ysgys4ov2JTN0Q1yh2BYA42l7w1cSnK5zW+H/jMz35xyXzww7F SazqCOPGI1FZi3nBnBa449EXvYXfO6qs2+5zcinf3BAJVEVvinNnUFApZk7UdbSl9lvP 4MlVkAtR8ue75uN9XZQ8O4+XAnrHVpjd5+aUa94qvSZ+2dPBL5bhZeXB4suHkx6CfMh7 BM2auKLLEZYHdkNUcvgAeF0gVQWZwqfdw1BdH3qp3lBicTkyuA+O1nTxxCpUysv71sFI az8xyxmn1hos0+YCYb7yBVYfOPE4ghSoOKW26cPN4+IuW2VgqbfK/eNfWOqgnOXJC+yd xZvw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references :user-agent:date:message-id:mime-version; bh=KlrSrEH3su+rQAAod9kDXqltooHkhuPda7kM3VfUrI0=; b=QJ9bYv3ayQErqn5JEReV9CBQ/Fe2HRqj5SNwzQdniSw4GWRUFkcML0zLMrCEE0uePI 3G6sRphEPd3OIG/YzHxdEk7cBqjo9AfYj4Bry4Uew0n99uES8U5BK1tssmJNlQ8kJusT Z/Jy/Ut5fUyJWNC4c5joHG+7VnOXDa6GWou6zfqNyMAtKS6rbazqqEa2tFFriXmeH+VO MeeLCrSjeNRH7///kdLe06WDINdM45TaBWG6zHBY0vY3vKuPZU58kdiXwsl+47pjzAhj iBAMzMonjKsOZgPphuzmglS+IabfmfdsT09qs9/P/EyxdXd1Bq3+ri8/1uMmfeunYToj WrbQ== X-Gm-Message-State: AIkVDXJKwNVGmyNBvPdBS3p0wpRjPGPFWWm31pDss49dqrgqu5WhvS0ffnSEVH6UAo/t+Q== X-Received: by 10.99.152.10 with SMTP id q10mr15448043pgd.106.1484900053195; Fri, 20 Jan 2017 00:14:13 -0800 (PST) Received: from garuda (c-24-18-189-215.hsd1.wa.comcast.net. [24.18.189.215]) by smtp.gmail.com with ESMTPSA id o18sm14359213pgn.36.2017.01.20.00.14.12 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 20 Jan 2017 00:14:12 -0800 (PST) From: Chris Marusich To: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: bug#25328: gpg: "Operation cancelled" with pinentry 1.0.0 on GNOME In-Reply-To: <877f64r3qg.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 09 Jan 2017 10:18:15 +0100") References: <87a8ba44d5.fsf@gmail.com> <877f64r3qg.fsf@gnu.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) Date: Fri, 20 Jan 2017 00:14:07 -0800 Message-ID: <87wpdqdu7k.fsf@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" X-Spam-Score: -1.8 (-) X-Debbugs-Envelope-To: 25328 Cc: 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: -1.8 (-) --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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=C3=A8s) writes: > For the record, I=E2=80=99ve never experienced this problem (that=E2=80= =99s 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-pin= entry-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=E2=80=99s 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. =2D-=20 Chris --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEy/WXVcvn5+/vGD+x3UCaFdgiRp0FAliBxtAACgkQ3UCaFdgi Rp23cxAAplBsoKlZkTu3H5rlBerNyCyr2yPReJZ5vZNb7nyu0VaflkStCIyIIveG y+DWu5y5PVtgxS5k1i9y/eX0CQQBZo7kP1fdVBbz7cMqKSCQoj36EN2h2VITIkRe /8U7XvmBmj5XVeBPIopuAaUHTIbOi0wtioeLZFJ1IDAdSEpDaZSRwh707dZ5Xb70 u/kFK7dS+uXDEkYTcsxaEQC7O/j94QERYSUdE46CbmPPSLUxzh3S8PN3KoCCFoQB SIsU+VsAB6bns5gcNy97B1XymnEapsivnwes6VgztiGvI6FNX9E7Fx34TuIb62Gy bFoTBNL47TQZulpVVq+PAZXvK4QbeHemLTghcGzDw7yolWJs21ELCRYjx7OIVvP5 yKcJdBF0Esm6vmt8QPhh6XjbQ/tuGmCwTc2w/jlgNsYL6byBEriZrmmSDyC1u8CV XoImxaVEoCwzuf9WSG+PRXvtdz1rCPaf+IY3D9v71V7DUY1j3Y9ykZIfQRvfI7bY 7Rx9EVWVhnTMtW6aUZB65b8sOg5TFZh1DqVg/r9ud6IgJv5JASKTL/faUYB+mql2 olMkNnCaO0KbTIWCq/7zyIXdY/IkVxPbQor5eN/AIQtrNHDpMZ6THbVtIla7g2J/ axHio6TuQeh2JNFtLJFMINf5JqtozniLvH9APSu2+OgSJNJdSXQ= =6bNS -----END PGP SIGNATURE----- --=-=-=-- 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. From debbugs-submit-bounces@debbugs.gnu.org Fri Jan 20 07:39:30 2017 Received: (at 25328) by debbugs.gnu.org; 20 Jan 2017 12:39:30 +0000 Received: from localhost ([127.0.0.1]:36087 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cUYTa-0003o7-4N for submit@debbugs.gnu.org; Fri, 20 Jan 2017 07:39:30 -0500 Received: from eggs.gnu.org ([208.118.235.92]:51859) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cUYTX-0003nt-4I for 25328@debbugs.gnu.org; Fri, 20 Jan 2017 07:39:27 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cUYTO-0003kU-RN for 25328@debbugs.gnu.org; Fri, 20 Jan 2017 07:39:21 -0500 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on eggs.gnu.org X-Spam-Level: X-Spam-Status: No, score=-2.4 required=5.0 tests=BAYES_50,RP_MATCHES_RCVD autolearn=disabled version=3.3.2 Received: from fencepost.gnu.org ([2001:4830:134:3::e]:37177) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cUYTO-0003kO-NW; Fri, 20 Jan 2017 07:39:18 -0500 Received: from [193.50.110.143] (port=39386 helo=ribbon) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1cUYTO-0002hM-1s; Fri, 20 Jan 2017 07:39:18 -0500 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) To: Chris Marusich Subject: Re: bug#25328: gpg: "Operation cancelled" with pinentry 1.0.0 on GNOME References: <87a8ba44d5.fsf@gmail.com> <877f64r3qg.fsf@gnu.org> <87wpdqdu7k.fsf@gmail.com> X-URL: http://www.fdn.fr/~lcourtes/ X-Revolutionary-Date: 1 =?utf-8?Q?Pluvi=C3=B4se?= an 225 de la =?utf-8?Q?R?= =?utf-8?Q?=C3=A9volution?= X-PGP-Key-ID: 0x090B11993D9AEBB5 X-PGP-Key: http://www.fdn.fr/~lcourtes/ludovic.asc X-PGP-Fingerprint: 3CE4 6455 8A84 FDC6 9DB4 0CFB 090B 1199 3D9A EBB5 X-OS: x86_64-unknown-linux-gnu Date: Fri, 20 Jan 2017 13:39:15 +0100 In-Reply-To: <87wpdqdu7k.fsf@gmail.com> (Chris Marusich's message of "Fri, 20 Jan 2017 00:14:07 -0800") Message-ID: <878tq5ewi4.fsf@gnu.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-Spam-Score: -8.2 (--------) X-Debbugs-Envelope-To: 25328 Cc: 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: -8.2 (--------) Hi Chris, Chris Marusich skribis: > 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. Could you report these steps upstream? That does not seem to be Guix-specific, though I suppose other distros probably install pinentry-gnome3 automatically when you install GNOME, such that the problem doesn=E2=80=99t show up. >> ISTR that GNOME has a hack to force its own Pinentry tool. Could it be >> what=E2=80=99s at fault? > > Where can I find more info about this hack? I did some Internet > searches, but I couldn't find anything specific. The =E2=80=9Chack=E2=80=9D I was referring to is probably just pinentry-gno= me3. > 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. It seems like bad interaction between pinentry-gtk2 and GNOME. On this topic, I found . Strangely, that bug discusses the opposite problem. :-) Ludo=E2=80=99. From debbugs-submit-bounces@debbugs.gnu.org Sat Jan 21 05:38:41 2017 Received: (at 25328) by debbugs.gnu.org; 21 Jan 2017 10:38:41 +0000 Received: from localhost ([127.0.0.1]:36886 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cUt4C-0002gC-Qh for submit@debbugs.gnu.org; Sat, 21 Jan 2017 05:38:41 -0500 Received: from mail-pf0-f194.google.com ([209.85.192.194]:33478) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cUt4B-0002fw-3r for 25328@debbugs.gnu.org; Sat, 21 Jan 2017 05:38:39 -0500 Received: by mail-pf0-f194.google.com with SMTP id e4so7007885pfg.0 for <25328@debbugs.gnu.org>; Sat, 21 Jan 2017 02:38:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version; bh=A+8UQ5RFm7hU6U8qr2gDktz+GXZQaszUetYlbh9He4Q=; b=ai1DPOipspccncv3Fbp3Vvs7ckGnuy9pOgr1qSw0NU6qARXJ7CX37EclWDrio+QWRW cBEPtzdGKBnsLJV919qlc2knSrdWF2ntYW2kP0NYHDs64oRwMt1MYnq0CppudmbzzsDg /yacAW1ysrZ1fbrNt1+mX0f+AYuDztC5tP4X7zr2NiS3aSesPoniIZc8bL1CIyk7G2Az rqNAb6NoESBrbIDWo8ZW+NJpTGDdhnTEH/J8fK9tTi8LzZmhIq5u9PHDIiHlMvwBcFLN od8z8YPq0a1dEdSVquvvyy44l0p3YyDugo41ArPqwRfMRZvhVILG7bJR+wg0y56ia6K1 7x0w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version; bh=A+8UQ5RFm7hU6U8qr2gDktz+GXZQaszUetYlbh9He4Q=; b=DmzKZbgyeGAvOuPReiKBsA4hnIlyNPnnM0GAwbhJU+MOzNjfijEIw1JtiNTXjZqkTq e/VHEUUlDr4RfbVFbDEaraW3o2e0UiGZm4j7DAi1DTUI+vICLiTvxjKOzVvcs/N5huf9 HNWFnx2mi6tFathCJZXPlChfEiBZr9BcS41EqVf1wcRn1HIYW6q/BDWe35EXAG73/CPk TOS7Z6TcDTM0LiamEi0DGVR0as6zI+AQngWXceVVXVHzvahIO2M9SUp3YLWPkXh/pgDt 3chVteAbJTSk7fh8OfF72X7ZoMTRIwYSIbZ7Zssv4oTsC0rA3mApqFyANwmOjiTpMpCW SMpA== X-Gm-Message-State: AIkVDXJL3hx05MFK+ghjW3H7ELnUGNLHoIu/Ws66k0kpBgldb56pVlldY8ibm/fbU9C9QA== X-Received: by 10.98.71.7 with SMTP id u7mr22188503pfa.76.1484995113266; Sat, 21 Jan 2017 02:38:33 -0800 (PST) Received: from garuda (c-24-18-189-215.hsd1.wa.comcast.net. [24.18.189.215]) by smtp.gmail.com with ESMTPSA id m29sm4772640pfi.54.2017.01.21.02.38.32 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sat, 21 Jan 2017 02:38:32 -0800 (PST) From: Chris Marusich To: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: bug#25328: gpg: "Operation cancelled" with pinentry 1.0.0 on GNOME References: <87a8ba44d5.fsf@gmail.com> <877f64r3qg.fsf@gnu.org> <87wpdqdu7k.fsf@gmail.com> <878tq5ewi4.fsf@gnu.org> Date: Sat, 21 Jan 2017 02:38:28 -0800 In-Reply-To: <878tq5ewi4.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Fri, 20 Jan 2017 13:39:15 +0100") Message-ID: <8737gc66l7.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" X-Spam-Score: -0.6 (/) X-Debbugs-Envelope-To: 25328 Cc: 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.6 (/) --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable ludo@gnu.org (Ludovic Court=C3=A8s) writes: > Could you report these steps upstream? That does not seem to be > Guix-specific, though I suppose other distros probably install > pinentry-gnome3 automatically when you install GNOME, such that the > problem doesn=E2=80=99t show up. I've sent an email to gnupg-devel@gnupg.org asking for help. I'll update this bug report when I have more to report. > The =E2=80=9Chack=E2=80=9D I was referring to is probably just pinentry-g= nome3. I see. >> 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. > > It seems like bad interaction between pinentry-gtk2 and GNOME. > > On this topic, I found > . Strangely, > that bug discusses the opposite problem. :-) Weird. I'm not sure how to approach bugs like this. I could strace in the dark and hope to see something that shows me the light, but hopefully the gnupg email list will know better how to troubleshoot it. =2D-=20 Chris --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEy/WXVcvn5+/vGD+x3UCaFdgiRp0FAliDOiUACgkQ3UCaFdgi Rp1/XA/9HCJYfMZzxKkb7hK4HL9nu5GBJsh/gwBnVuyO62Yn3IY3CBJRbbKUUoeg dZvP7dzS1E02PQlzkAbjEPN6sGgsFksqANEZOfb+UGzi2YEn8DqzWOFYoy7RE9JX sarIS2fGdTe2dF3WxuOS6FF7U4HeMrmfF5cgDudMI8u1xsbMeGRD6uxmGzK6p0JK bRM/8HkZRM1QRpxZ0OjeHNtFO8/6xnc0xt56r/Hbxj+zDDEEQtqlfzpS5PhEOogS 4c7hSYIpSRSRFqTgZM/8FgBJ+BXsP3h1le9/yH0cCCcw6NTgKfYaHLmafSkKgvXF w4syiOfcTUOPVwwfsM1TYszvFioYZKi0OR/t9h/PBfAhx/kmfG2oSe9Lf3Z3npJf SWCVMA7q+iC4rxb83+J0nBA03UihDgZkPgOdkuAGjVpQ5QVu6iOe8L8ONha3GIxv guV9EGU+02e/zjaQeLA5XHoLfyEN+JPrc1UvXvjscYYa8N3NTcg0aShejhoBgx32 JZlfVg604P5lXgCz7iEpikw+y9NNPIa9Sed9VjVmFL+sOgS5pu47jaf4InR2K+m/ WJ3a6Xa8JN7d2KzsRxns/AEvVY0gZa94J47WfNB9V9hzQy2XbIxVDLVzyWNfKKj8 12EuRz6wyP4yrIiArSWk8TKsTdkx+T8pR/peoAsyAOCv2lc9Hog= =9Sg0 -----END PGP SIGNATURE----- --=-=-=-- From debbugs-submit-bounces@debbugs.gnu.org Sun May 07 16:51:12 2017 Received: (at 25328) by debbugs.gnu.org; 7 May 2017 20:51:12 +0000 Received: from localhost ([127.0.0.1]:60825 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d7T96-0004pM-5m for submit@debbugs.gnu.org; Sun, 07 May 2017 16:51:12 -0400 Received: from mail-pg0-f43.google.com ([74.125.83.43]:34803) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d7T94-0004pA-MX for 25328@debbugs.gnu.org; Sun, 07 May 2017 16:51:11 -0400 Received: by mail-pg0-f43.google.com with SMTP id u28so12654866pgn.1 for <25328@debbugs.gnu.org>; Sun, 07 May 2017 13:51:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:in-reply-to:references:user-agent:date :message-id:mime-version; bh=5mYpPVfW+ZUNldDRUL3W5EVedxAQLDwxKzs32PVjcSU=; b=nPuXQ7MkRyq5JBppsweaqjqDl7HJQuUgLBvdvBq70QksZv8gutJtC3lrj+TuM/zpHU 7G/dqYIdZLwtbdgeXb9mj7HL/3QOw8jJwbSfsyCbIpUZx1yFCFotVaiAfz+YNP4DjUFL jC//oAI9d+vlUEL6YjWRLWgjRXyk5HFj3XhFZTofnaHz3gwP/usFOR+2n2pboEQiaY0e KuRMacjOH5OGAFyfWauttKumwj6hVc/R03eSpPqLhgKXMs7Dv4yq9+jAwqw+oJarKVUO HVGIOCKjZAlAsXjxGqHBpGUM+qm74TGBTgZxrYDYQtZ72uBNlYVBlrxhcnO3vz29HTxU Zjxg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references :user-agent:date:message-id:mime-version; bh=5mYpPVfW+ZUNldDRUL3W5EVedxAQLDwxKzs32PVjcSU=; b=XxITNZkOVyBej51DJ6aqCXBG2PtNtON/wVBgWcGs5eePTlRTd2Re0nA1v/2HMyo2d0 sXZKXkPzt6VjGqA/Dq4W3kHFj9x7dN4WICjw0LcrNB/86HHDaH6W0Z55STbJ6tQ3oV+v WrYgHBCIK/hLf8phbzbEHjoq7xrwsz6TJ/4dYlzW9wU3s641bjJU+uDt9avJ1hZxDB/k wZCf3J19rIrs7DIrRgAStDAEf5J6Advs5LEvVjzKsVkRJjzURAQent1UjZcTYKnu7bNq 5nVj0TuR8T7LiqzJK++icx7ZjFTnQSxX3VIChnYaKtaXoZujksq2G2pg4b4GqL2TJqRf K1WQ== X-Gm-Message-State: AN3rC/7IHs2r15xWm7Dd2vuOKEOzRcmYOcCR7GVpWrGLg/XTPEoAzF+G qleLm2boRfvtTQ== X-Received: by 10.98.77.135 with SMTP id a129mr27889547pfb.95.1494190264750; Sun, 07 May 2017 13:51:04 -0700 (PDT) Received: from garuda (c-24-18-189-215.hsd1.wa.comcast.net. [24.18.189.215]) by smtp.gmail.com with ESMTPSA id q6sm19557967pfq.18.2017.05.07.13.51.03 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 07 May 2017 13:51:03 -0700 (PDT) From: Chris Marusich To: gnupg-devel@gnupg.org Subject: Re: pinentry-gtk-2 fails after upgrade to 1.0.0: "Operation cancelled" In-Reply-To: <877f5o6e1d.fsf@gmail.com> (Chris Marusich's message of "Fri, 20 Jan 2017 23:57:34 -0800") References: <877f5o6e1d.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux) Date: Sun, 07 May 2017 13:50:59 -0700 Message-ID: <87tw4wtmq4.fsf@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" X-Spam-Score: -2.8 (--) X-Debbugs-Envelope-To: 25328 Cc: 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: -2.8 (--) --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Chris Marusich writes: > Hi, > > Since upgrading pinentry-gtk-2 from 0.9.7 to 1.0.0, I've noticed some > strange behavior. Whenever I try to do something that requires access > to my secret key, no window appears, and I get an error like the > following: > > $ gpg --sign /tmp/message=20 > gpg: signing failed: Operation cancelled > gpg: signing failed: Operation cancelled > $=20 > > Is this expected behavior with 1.0.0? > > This happens about 90% of the time. About 10% of the time, a pinentry > window actually does pop up. When using version 0.9.7, a pinentry > window popped up 100% of the time. I expected the behavior of 1.0.0 to > be the same. > > My software versions are: > > * GuixSD 0.12.0 > * GNOME 3 (GNOME shell 3.22.2) > * gnupg 2.1.16 > * pinentry-gtk-2 1.0.0 > > My ~/.gnupg/gpg-agent.conf file contains the following single line: > > pinentry-program /home/marusich/.guix-profile/bin/pinentry-gtk-2 > > When I change my gpg-agent.conf file to use pinentry-gnome3 , > pinentry-curses, or pinentry-tty (and I kill gpg-agent to make sure it > uses the modified file), the problem doesn't occur. > > When I keep pinentry-gtk-2 in my gpg-agent.conf file, and I log into an > Xfce session, the problem doesn't occur. Likewise, when I log in via a > virtual terminal (e.g. the kind you can get by pressing Control+Alt+F2), > the problem doesn't occur. > > In other words, the problem only seems to occur when I use > pinentry-gtk-2 as my pinentry-program, and I'm logged into a GNOME 3 > session. The problem occurs regardless of what program I am running > inside of that GNOME 3 session; for example, it happens in emacs when > emacs tries to automatically decrypt files ending in ".gpg", too. > > Here's how to 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. > > * Open up any terminal (GNOME terminal and emacs' "M-x term" will both > reproduce the issue) to sign a message, e.g.: > > echo hello > /tmp/message > gpg --sign /tmp/message > > You should get the error very frequently. Did anybody get this message? I sent it in January of 2017, but I can't find it in the online archives, so I'm worried maybe it never got delivered: https://lists.gnupg.org/pipermail/gnupg-devel/ This time, I've CC'd 25328@debbugs.gnu.org so that my email gets delivered to at least one location for posterity. =2D-=20 Chris --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEy/WXVcvn5+/vGD+x3UCaFdgiRp0FAlkPiLMACgkQ3UCaFdgi Rp2keg/9FfBPfT7fJECQ6ULV/UhMZJ3av2WR9sbWGcAcuPp8dN0HL/ePewWb0Oq1 0ObJDrexo0pWJaV6jbmHbVqG+JYbnUtI2VzKSmif9mIa2gZeJnTuOqfT1cv51/zb xI4njpGWxGOU0erlju2XzlxVtd+dNPG5Y4cugNlwwWYjdOHNsK5sJdIT1Zk3rZJD 17xCdbOwNyQb3SaOD+IP2tVeTtoYOWY+FT8CGhpaQR+C8kDIdF5iBaGPYnYbaEmg Zda3+HJWLyn2uueYIHJyMtGiQ9GpSNjRz/yzh+2ElnZ0MR7uarDQzRHbJwsgmg3M IsgRO2pXE+iw9khrLsFcan/aU+qlPirTDQz19LRs8r5WzGheZZhqTxj3e3SfG31h ly3aByW/35Xf6CwYlIKPjM/h9ADutqHhE6yMWT1YPXKAcIq7g+JIInWjzz5oyOfU QKzrLzqCXNXnO2R5nVxNW/bGRiJNvJC41Z9P3biQfmS13g7VwoDTK4kupj8r6VEQ G7pP0ODo3lR1uzkUteFamwcptsYfnxkzXs29MzAMK6RkUx/jBtO2RGAkMUnorf0U KgyEVrNlTUDKcYaoRI8TthpqF810PkH2iBr1Mv0udSBP/wT1Wu4qcwvAZOsE0/Vk Zb5kBHW0YmcDl12cevo93IFqgk9mkEdCuTSSnLFlYii1efJnG7A= =NMwF -----END PGP SIGNATURE----- --=-=-=-- From debbugs-submit-bounces@debbugs.gnu.org Sun May 07 18:16:12 2017 Received: (at 25328) by debbugs.gnu.org; 7 May 2017 22:16:12 +0000 Received: from localhost ([127.0.0.1]:60881 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d7UTM-0006pO-Ci for submit@debbugs.gnu.org; Sun, 07 May 2017 18:16:12 -0400 Received: from o130.p8.mailjet.com ([87.253.233.130]:53699) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from <42903767.AEQAKKXjfu8AAAAAAAAAAAO8QtMAAAACwQwAAAAAAAW9WABZD5yp@bnc3.mailjet.com>) id 1d7UTK-0006pE-AP for 25328@debbugs.gnu.org; Sun, 07 May 2017 18:16:10 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/simple; q=dns/txt; d=bnc3.mailjet.com; i=arunisaac=3Dsystemreboot.net@bnc3.mailjet.com; s=mailjet; h=message-id:mime-version:from:to:subject:date:list-unsubscribe:in-reply-to: references:x-csa-complaints:x-mj-mid:content-type:content-transfer-encoding; bh=68cBBFyIWbwiqOSjI2kxS1IRQ4E=; b=gltVwBYgmcmWbkzoqIyN56qO65DxbUXRUi1rv1Ox1mOTA0CtL1tWpgXKs bMR3ZelhTYr/+npYqHkfErTNC0yx6U0p4gQaWF9hNJIy9vHvZtZdIJ6d8dQ2 NDWV5PkTcKJzpmfA9k4xTDNWJlbsBlPUpwXXovAfXvu4yRKe6+AhSc= Message-Id: <42903767.AEQAKKXjfu8AAAAAAAAAAAO8QtMAAAACwQwAAAAAAAW9WABZD5yp@mailjet.com> MIME-Version: 1.0 From: Arun Isaac To: 25328@debbugs.gnu.org Subject: Re: bug#25328: pinentry-gtk-2 fails after upgrade to 1.0.0: "Operation cancelled" Date: Mon, 08 May 2017 03:45:40 +0530 In-reply-to: <87tw4wtmq4.fsf@gmail.com> References: <877f5o6e1d.fsf@gmail.com> <87tw4wtmq4.fsf@gmail.com> X-CSA-Complaints: whitelist-complaints@eco.de X-MJ-Mid: AEQAKKXjfu8AAAAAAAAAAAO8QtMAAAACwQwAAAAAAAW9WABZD5ypR3BnUpIrR6aGDUgUbptjjgAFgUc Content-Type: text/plain Content-Transfer-Encoding: quoted-printable X-Spam-Score: -2.8 (--) X-Debbugs-Envelope-To: 25328 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: -2.8 (--) >> Since upgrading pinentry-gtk-2 from 0.9.7 to 1.0.0, I've noticed some >> strange behavior. Whenever I try to do something that requires access >> to my secret key, no window appears, and I get an error like the >> following: >> >> $ gpg --sign /tmp/message >> gpg: signing failed: Operation cancelled >> gpg: signing failed: Operation cancelled I am experiencing the exact same problem with pinentry-gtk-2 in exwm (Emacs X Window Manager). The pinentry window seems to get closed immediately after it appears. I thought that this was some bug in exwm. But, now that you mention this, maybe something's wrong with pinentry-gtk-2. = From debbugs-submit-bounces@debbugs.gnu.org Sun May 07 19:34:02 2017 Received: (at 25328) by debbugs.gnu.org; 7 May 2017 23:34:02 +0000 Received: from localhost ([127.0.0.1]:60925 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d7Vgg-0000B9-0T for submit@debbugs.gnu.org; Sun, 07 May 2017 19:34:02 -0400 Received: from out4-smtp.messagingengine.com ([66.111.4.28]:43079) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d7Vge-0000Al-Me for 25328@debbugs.gnu.org; Sun, 07 May 2017 19:34:00 -0400 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 933042063D; Sun, 7 May 2017 19:34:00 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Sun, 07 May 2017 19:34:00 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=famulari.name; h=cc:content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-me-sender:x-me-sender:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=Zl1gYWOtx60Sf6K/2tva4rt1q1jrthhrwRZcn/ bvjqI=; b=OdR5T8zivVEXSt+I+qIJ9sAzCa98d8PRSi7PXAo3xRtNOU5ocOHl5T ZKfsM5pJbvu25vOy3oT1YMAD2d3iwRB1FxRJfVOTXxAPrwMdyBf34FfAp18W6Pvy 4WfsUFH/kab4PNz5j4H5t1OmrfpZKCi8Pj+HQlZoMVC1yGpmTTnPo= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=fm1; bh=Zl1gYWOtx60Sf6K/2t va4rt1q1jrthhrwRZcn/bvjqI=; b=duTlF3NcHGTqQwegDMuWjsCK9151Pv/Zjz o71cZho96Hbv5+Fvoj9/36Mb+h1crC/mLjiRfNo7kO/pxSz7nLLl+SdPkdAuy3XA 26vGQS25v0HAcW5s8ZZYxyY6BsG0BHrVxLCTcUchMTrFp28ZcMRnXPvwdKq4fj27 jkLw0RbqsQ3mw73qDNXx2iYvbVll+QIAn4FO6dRUHW6bL2wt0vnk1sOvTSnqtl4/ 1wUKLSUUxBsgXLeQSDbqr6+I8t3F5wVoaHOBM/BtpqZTzVh0IgPKunVTSjJbHBUl DRuShlLTB+SFOp5bcWr+blmx3JAFXsZiZKwanK2+7yWBjCjb4TJg== X-ME-Sender: X-Sasl-enc: krzii5EuNH6oYmhwJKBTCIuP0WcJOPRU2f+qKSP3vNoG 1494200040 Received: from localhost (c-73-165-108-70.hsd1.pa.comcast.net [73.165.108.70]) by mail.messagingengine.com (Postfix) with ESMTPA id 3D151241E3; Sun, 7 May 2017 19:34:00 -0400 (EDT) Date: Sun, 7 May 2017 19:33:59 -0400 From: Leo Famulari To: Arun Isaac Subject: Re: bug#25328: pinentry-gtk-2 fails after upgrade to 1.0.0: "Operation cancelled" Message-ID: <20170507233359.GA20778@jasmine> References: <877f5o6e1d.fsf@gmail.com> <87tw4wtmq4.fsf@gmail.com> <42903767.AEQAKKXjfu8AAAAAAAAAAAO8QtMAAAACwQwAAAAAAAW9WABZD5yp@mailjet.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="VS++wcV0S1rZb1Fb" Content-Disposition: inline In-Reply-To: <42903767.AEQAKKXjfu8AAAAAAAAAAAO8QtMAAAACwQwAAAAAAAW9WABZD5yp@mailjet.com> User-Agent: Mutt/1.8.2 (2017-04-18) X-Spam-Score: -0.7 (/) X-Debbugs-Envelope-To: 25328 Cc: 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 (/) --VS++wcV0S1rZb1Fb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 08, 2017 at 03:45:40AM +0530, Arun Isaac wrote: > >> Since upgrading pinentry-gtk-2 from 0.9.7 to 1.0.0, I've noticed some > >> strange behavior. Whenever I try to do something that requires access > >> to my secret key, no window appears, and I get an error like the > >> following: > >> > >> $ gpg --sign /tmp/message > >> gpg: signing failed: Operation cancelled > >> gpg: signing failed: Operation cancelled >=20 > I am experiencing the exact same problem with pinentry-gtk-2 in exwm > (Emacs X Window Manager). The pinentry window seems to get closed > immediately after it appears. I thought that this was some bug in > exwm. But, now that you mention this, maybe something's wrong with > pinentry-gtk-2. Chiming in to say that Guix's pinentry-gtk-2 works fine for me on Debian unstable. --VS++wcV0S1rZb1Fb Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAlkPrucACgkQJkb6MLrK fwhogw//c3wKwC7TjFSEC3pU0BokZAKUr8Qrubfvi7+ZAMnY2EhwT52k4VxUMHWS BcF0SEPTJ35+T+iF7oFPEkieTdZKfkqPmEQ4dcc8scpUPRPAf+sWAeZI26dt7Ia1 inhSPMMjcV9f0OpIoSITnmQcatHADTdizIGJr7SAAr/zyfBk9F/tVF+G3C2AF2Cp T0Cgp33Tbl/RQsCo85Rqs+mCXXypsFzWHogDvCxMaflACvtSTZiMbrQjfitaXMYY 2yJQ+uwcuY/dbZTOiCq+XD1gXmY/hKiCd27dLJqNedLPkrevBvrp1imPd3UHY8pd /hzqcuN6AGhVW6iI7Tm9vXcGLVLLUeQmSL97947kcQTUtI6p2BMpQLacIRy0/L1X iPjtr103NS8zbajsMIXp2wpHasTfaEf9Vi5MDua3a6eJ+yF9Q/AYiF3tpygBC9ml dU0L4H0dULLVyWM7F17/oEcFzsUZJRa3LOzZ6JbnhUxNAohoqzXbZHE53Z3DH/9I A/3mITVmvN7wvBb5JDIqVg2TfW0s3j0zjG8IwY8Ykbdu1OSytrUhrb4dteg1zfQg bWfQWvdZXQiCBDK1N1yG54p+9+KAvRy5p8tBEacLfxTTFrrd1P0ISWMCE4263QMB URnhdhBgJMN3cYjECtcKuwvjtbKD7zVTrDnF/bgWZGsLqKjzGgo= =t4+P -----END PGP SIGNATURE----- --VS++wcV0S1rZb1Fb-- From debbugs-submit-bounces@debbugs.gnu.org Wed May 10 03:47:00 2017 Received: (at 25328) by debbugs.gnu.org; 10 May 2017 07:47:00 +0000 Received: from localhost ([127.0.0.1]:35002 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d8MKq-0006kE-IX for submit@debbugs.gnu.org; Wed, 10 May 2017 03:47:00 -0400 Received: from mail-pf0-f170.google.com ([209.85.192.170]:35830) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d8MKp-0006k0-9X for 25328@debbugs.gnu.org; Wed, 10 May 2017 03:47:00 -0400 Received: by mail-pf0-f170.google.com with SMTP id v14so12040400pfd.2 for <25328@debbugs.gnu.org>; Wed, 10 May 2017 00:46:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:subject:references:date:in-reply-to:message-id:user-agent :mime-version; bh=G6CWSvUqbuPqwd3/pq2OGM3KEQbHzaQdwPynKy+9Qww=; b=EPlq3Oc+KSL3iConzMRTFOyeWGQdnzYG6CL0pcESvLGRp+mR2940kw2u5ZoaZO5j2p stUoNvrqWHsUAAdxR69mcACzN43T/hKUs//VUYtgBbTREUsBI+r4G9NsfhCzWfHvDcXy K6lLBtWavQCPTPVOQSaSUgJj3Q3NWwJuNMBdIBYwftcMDYO+TehChIS8Pv7eup8HoR/p /P0HoKR1te0WkVJA2hcVHksSU8Kl6YSE96SlofNfTDNRF0f9ETB/dnMW3aXc1Y3R8Hik +Cz9v7ClRmJnyFJDFetUTI2FlWL8ZtJeQbtWkr8jSc73FPf/nGQb+fK642rrHSVXICdQ zfJA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:references:date:in-reply-to :message-id:user-agent:mime-version; bh=G6CWSvUqbuPqwd3/pq2OGM3KEQbHzaQdwPynKy+9Qww=; b=KRp9qrraSD8l5JJGs76PaNQWLdfa/tfnS370h3UdbfZYUEEiesVbtry98LKtmTkA3J u0rBpQkMb0gJ9VSCH6M42l+5xSE1kv8qktexoDae6W8eoDGz8AYoavZwmuMigFuC0XP3 kIENCak/5YCq/WPN0jYxxXn4p44siGhGcdVHMSQdGn0UUiGvPxvJmblfmb4wxUAWuCoU C31UaodinvhuU/k6f82kf8jIesBFYjLRSaXithOJeE9hqoK/f2NI/cEr3g1wyzC2J1I2 LFEKOUsdt1qzOBvDgAHcZsrJDEWp7YRuyhk8lTso88xFqzuiYmlrl9xqDnQ53V3KlA9+ PBNg== X-Gm-Message-State: AODbwcAy6tU1MOVc9dwJq5bVoRRXybvWQ8WWwdji03Jc7Fg0t+rIicc0 3oG82FIXja908bs6 X-Received: by 10.98.9.92 with SMTP id e89mr4561908pfd.177.1494402412683; Wed, 10 May 2017 00:46:52 -0700 (PDT) Received: from garuda (c-24-18-189-215.hsd1.wa.comcast.net. [24.18.189.215]) by smtp.gmail.com with ESMTPSA id r21sm3938643pfg.95.2017.05.10.00.46.51 for <25328@debbugs.gnu.org> (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 10 May 2017 00:46:51 -0700 (PDT) From: Chris Marusich To: 25328@debbugs.gnu.org Subject: Re: bug#25328: pinentry-gtk-2 fails after upgrade to 1.0.0: "Operation cancelled" References: <877f5o6e1d.fsf@gmail.com> <87tw4wtmq4.fsf@gmail.com> Date: Wed, 10 May 2017 00:46:50 -0700 In-Reply-To: <87tw4wtmq4.fsf@gmail.com> (Chris Marusich's message of "Sun, 07 May 2017 13:50:59 -0700") Message-ID: <8737cd5f2t.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 25328 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: -2.3 (--) --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Chris Marusich writes: > Chris Marusich writes: > >> Hi, >> >> Since upgrading pinentry-gtk-2 from 0.9.7 to 1.0.0, I've noticed some >> strange behavior. Whenever I try to do something that requires access >> to my secret key, no window appears, and I get an error like the >> following: >> >> $ gpg --sign /tmp/message=20 >> gpg: signing failed: Operation cancelled >> gpg: signing failed: Operation cancelled >> $=20 >> >> Is this expected behavior with 1.0.0? >> >> This happens about 90% of the time. About 10% of the time, a pinentry >> window actually does pop up. When using version 0.9.7, a pinentry >> window popped up 100% of the time. I expected the behavior of 1.0.0 to >> be the same. >> >> My software versions are: >> >> * GuixSD 0.12.0 >> * GNOME 3 (GNOME shell 3.22.2) >> * gnupg 2.1.16 >> * pinentry-gtk-2 1.0.0 >> >> My ~/.gnupg/gpg-agent.conf file contains the following single line: >> >> pinentry-program /home/marusich/.guix-profile/bin/pinentry-gtk-2 >> >> When I change my gpg-agent.conf file to use pinentry-gnome3 , >> pinentry-curses, or pinentry-tty (and I kill gpg-agent to make sure it >> uses the modified file), the problem doesn't occur. >> >> When I keep pinentry-gtk-2 in my gpg-agent.conf file, and I log into an >> Xfce session, the problem doesn't occur. Likewise, when I log in via a >> virtual terminal (e.g. the kind you can get by pressing Control+Alt+F2), >> the problem doesn't occur. >> >> In other words, the problem only seems to occur when I use >> pinentry-gtk-2 as my pinentry-program, and I'm logged into a GNOME 3 >> session. The problem occurs regardless of what program I am running >> inside of that GNOME 3 session; for example, it happens in emacs when >> emacs tries to automatically decrypt files ending in ".gpg", too. >> >> Here's how to 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. >> >> * Open up any terminal (GNOME terminal and emacs' "M-x term" will both >> reproduce the issue) to sign a message, e.g.: >> >> echo hello > /tmp/message >> gpg --sign /tmp/message >> >> You should get the error very frequently. > > Did anybody get this message? I sent it in January of 2017, but I can't > find it in the online archives, so I'm worried maybe it never got > delivered: > > https://lists.gnupg.org/pipermail/gnupg-devel/ > > This time, I've CC'd 25328@debbugs.gnu.org so that my email gets > delivered to at least one location for posterity. Looks like I might need to be subscribed to gnupg-devel in order to post to it, so I've subscribed for this purpose. I'll update this bug report again if my message actually shows up in the gnupg-devel list. =2D-=20 Chris --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEy/WXVcvn5+/vGD+x3UCaFdgiRp0FAlkSxWoACgkQ3UCaFdgi Rp3Xvg//ceRt0JzKveu6ycEbk5VOjFyWE2K7ufqIZLQw8iqQcATii9vQ5xyDkFJi VzqiyEgcF9Tw1fOKyKqVeqTIBrAYMNRS8ZsCZvOVzvYr+QN2C4dYggQfrkqyrXtj NStzgY/F4h1RpBI/pSFQOBsIriPcK+/xN3A65r6oD80D1dF7oQPPZxXUNXUEBnku o3hm/2PK+SrBCmxk9v9Nfauh1pVJkkXEbCTXTxoZe5ms3VXi18ej9TfGUKXwfwT1 YRVK+Kk0p3jw1z8p2Zsj7NoXRq+nqh08qiYl1d6pBU6k7rJ5ySgD9X+yclPjLDkT ZP1TX0eRJCwT0tRtphvV9z6iHMaStit0tCucV/1n2SWufPAFfjMmlzozsBK1P6x5 38tII1OKIYOaVBzNLklKBSN/+LzE8AOMv26dyP4A/fgN4rncvi0CwF7SkTZMVF4I SD1wQ9kmzepJMsawwqnQic3UEweP6vMR9JXpsNGzQkjZr+rbhngRdR7yLe/GCt8c eTxVCoxnDmugzm8jbhkpp3UY3CMeDX6sRe8bZ/T6zkWF6EwEHayy9mlYzt9uKLKS /QJqGS0PqeWmJ6ITJiPgirPFQE3WhOaW/FoFt1EyjqdqAlNlYJCQMJr34klCvHTZ /xcTIm7KcjC40Wb3bq7HsI3VuQjtbEqr8SG7vPnZyrqg4kfzlYc= =4trK -----END PGP SIGNATURE----- --=-=-=-- From debbugs-submit-bounces@debbugs.gnu.org Wed May 10 04:00:40 2017 Received: (at 25328) by debbugs.gnu.org; 10 May 2017 08:00:40 +0000 Received: from localhost ([127.0.0.1]:35022 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d8MY4-00074l-D4 for submit@debbugs.gnu.org; Wed, 10 May 2017 04:00:40 -0400 Received: from mail-pf0-f177.google.com ([209.85.192.177]:34643) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d8MY2-00074Y-Dp for 25328@debbugs.gnu.org; Wed, 10 May 2017 04:00:38 -0400 Received: by mail-pf0-f177.google.com with SMTP id e64so12229625pfd.1 for <25328@debbugs.gnu.org>; Wed, 10 May 2017 01:00:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version; bh=OwWfhE4ZcuhvIbvc0X4Tjjve3yITo9oyhL/TMF3Tmso=; b=NqizSd1DxDm8rvbWIPGqz3ViUTqFZwYruHuxF0hMOyE/Uf9sc2N56LxDgpwfIHO6kY bT3keIv5D0jqhKfcBCRF9f29a0y4AwfwdZIoErx9U4WS/4cFZ/jWNgSgaVh7nL6maaAS 0vVTx2nvlRHFrJB9r/iZMKdThi/WkFTZAYuRm/tWI2Og5ZCgR30d4DFcq9iN1KDkzHh6 0DaZolJhklIjzmhjcBwmaAiFup/x9eO0FW7D3xjdH1otuZQBOuqfJfeJngPmH5EXoFPB EpL7dxB87Db1XLkjCsQYX5jM/ZKnFVtnDz9bt9UaYgAgncdi9UnBLn3sWfbTNizwmgeI IbnA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version; bh=OwWfhE4ZcuhvIbvc0X4Tjjve3yITo9oyhL/TMF3Tmso=; b=KxhFFp+IzWg/BtkFTguRVvu74TwBjhD7E57J8zjLNjQQ7ZMzOTrQxEjAS47iy51qeT +hlwcoUGfAxErGUw3BdXBFqVRrM5+TAXaJsnCiez7rkeRgWqlb8BV+QuqbUL46vdiy6D 8YohXZ0wPjgr7e/amEk+ne5eNf2+J3cI3GNOEs0Jq1ByOXDHCIYip6EQD1675aKGE9Rr nyMQiPEjKSVvlw+ALKfRHpxUKRPSPz3aLh2Llc07eWsDmyK+wcOghc38ytK7bc0qx+I+ h2C2jqIApxUvsUBdIC82Pt6mQIMT5ThmQxl/kPRVNOOt+YvIgULtn24nWegpimK59ddM p/xA== X-Gm-Message-State: AODbwcDGaeWy9h3NMiACZAAwz0gJFcRVnehtFi+0RwrliGwJO64FA1Gt LAlFNhCh38Nt+XMY X-Received: by 10.98.66.214 with SMTP id h83mr4736775pfd.182.1494403232035; Wed, 10 May 2017 01:00:32 -0700 (PDT) Received: from garuda (c-24-18-189-215.hsd1.wa.comcast.net. [24.18.189.215]) by smtp.gmail.com with ESMTPSA id r90sm3652748pfl.82.2017.05.10.01.00.30 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 10 May 2017 01:00:30 -0700 (PDT) From: Chris Marusich To: gnupg-devel@gnupg.org Subject: Re: bug#25328: pinentry-gtk-2 fails after upgrade to 1.0.0: "Operation cancelled" References: <877f5o6e1d.fsf@gmail.com> <87tw4wtmq4.fsf@gmail.com> Date: Wed, 10 May 2017 01:00:29 -0700 In-Reply-To: <87tw4wtmq4.fsf@gmail.com> (Chris Marusich's message of "Sun, 07 May 2017 13:50:59 -0700") Message-ID: <87shkd3zvm.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" X-Spam-Score: -2.8 (--) X-Debbugs-Envelope-To: 25328 Cc: 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: -2.8 (--) --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Chris Marusich writes: > Chris Marusich writes: > >> Hi, >> >> Since upgrading pinentry-gtk-2 from 0.9.7 to 1.0.0, I've noticed some >> strange behavior. Whenever I try to do something that requires access >> to my secret key, no window appears, and I get an error like the >> following: >> >> $ gpg --sign /tmp/message=20 >> gpg: signing failed: Operation cancelled >> gpg: signing failed: Operation cancelled >> $=20 >> >> Is this expected behavior with 1.0.0? >> >> This happens about 90% of the time. About 10% of the time, a pinentry >> window actually does pop up. When using version 0.9.7, a pinentry >> window popped up 100% of the time. I expected the behavior of 1.0.0 to >> be the same. >> >> My software versions are: >> >> * GuixSD 0.12.0 >> * GNOME 3 (GNOME shell 3.22.2) >> * gnupg 2.1.16 >> * pinentry-gtk-2 1.0.0 >> >> My ~/.gnupg/gpg-agent.conf file contains the following single line: >> >> pinentry-program /home/marusich/.guix-profile/bin/pinentry-gtk-2 >> >> When I change my gpg-agent.conf file to use pinentry-gnome3 , >> pinentry-curses, or pinentry-tty (and I kill gpg-agent to make sure it >> uses the modified file), the problem doesn't occur. >> >> When I keep pinentry-gtk-2 in my gpg-agent.conf file, and I log into an >> Xfce session, the problem doesn't occur. Likewise, when I log in via a >> virtual terminal (e.g. the kind you can get by pressing Control+Alt+F2), >> the problem doesn't occur. >> >> In other words, the problem only seems to occur when I use >> pinentry-gtk-2 as my pinentry-program, and I'm logged into a GNOME 3 >> session. The problem occurs regardless of what program I am running >> inside of that GNOME 3 session; for example, it happens in emacs when >> emacs tries to automatically decrypt files ending in ".gpg", too. >> >> Here's how to 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. >> >> * Open up any terminal (GNOME terminal and emacs' "M-x term" will both >> reproduce the issue) to sign a message, e.g.: >> >> echo hello > /tmp/message >> gpg --sign /tmp/message >> >> You should get the error very frequently. > > Did anybody get this message? I sent it in January of 2017, but I can't > find it in the online archives, so I'm worried maybe it never got > delivered: > > https://lists.gnupg.org/pipermail/gnupg-devel/ > > This time, I've CC'd 25328@debbugs.gnu.org so that my email gets > delivered to at least one location for posterity. I can no longer reproduce this issue. I tried following the steps above on my current GuixSD system, and the problem does not occur. It seems like pinentry-gtk-2 works fine now, which is curious because the version is still 1.0.0. I don't know why it works now but didn't earlier. My emails never seem to have made it to the gnupg-devel list, but in this case I suppose it doesn't matter any more. I think we can resolve this bug report, unless someone else can reproduce the issue reliably. =2D-=20 Chris --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEy/WXVcvn5+/vGD+x3UCaFdgiRp0FAlkSyJ0ACgkQ3UCaFdgi Rp08KQ//WDdZpv6h6rS4vvjLNSpPp1wSddx8U3F5ruzD8Cm6vnK3teFDFo0Eb1g4 m0q29hohqt4hkYLKi/c1qkItVwWug/QwU7PTH2bWOkAzW1wYYdRaB/Ck/COKf6Ed FQnmQydd4cF/x/Pvk15VkThgDLw+uO3D2McqY53jmaIPp6k/R+Vz1ifYsleNim6Y w2CA8zE7A7MIaX8IUzS3TRIy3Qi1XNhKsffoDE5+YiHoEH8HACqVx96EQ8O0aRJv xOuoVZuthTrM8gQhGeRV33uoE2XMreW3tl6Olmf74gRO4w8wtwetEV/+Hw6nw3lu bJzG8qg6HJB2LzDZD6pFBMaUtALSMX25rxiwurVKZKjKqQ92h+4aG0iWuPZa4rLP i+0X24pP7V7oj0RJNXJjv0oUyTkg598rPpHmXXIyIBxDhH2cmdnCHhhNpWFjUWpT llQ29LRVosOG+qgzMn8W059pi302B/6Frd5xlHX2rQ1FMxDwSSvXkCp2n28kJ3+w 6RRl/KN58CMYftubqBO6a4BCssvabDCBclO7XZTBpN4J6Q/47KU2W2D4xHW0dCIV d5KSSsBtcS2xHrhFk82/8/2mkh0Unhn4y0hmuEYePiHukfqmUFLJj/WQtKhT8YLe QI/1ArMnVlJswJIxXMCe6QnL7C+1/m16RkqYlPN1c0ucdyFIabs= =x8Ei -----END PGP SIGNATURE----- --=-=-=-- From debbugs-submit-bounces@debbugs.gnu.org Wed May 10 08:07:02 2017 Received: (at control) by debbugs.gnu.org; 10 May 2017 12:07:02 +0000 Received: from localhost ([127.0.0.1]:35181 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d8QOT-00062M-RE for submit@debbugs.gnu.org; Wed, 10 May 2017 08:07:01 -0400 Received: from eggs.gnu.org ([208.118.235.92]:55769) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d8QOT-00061y-40 for control@debbugs.gnu.org; Wed, 10 May 2017 08:07:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d8QOK-0006xq-2g for control@debbugs.gnu.org; Wed, 10 May 2017 08:06:55 -0400 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on eggs.gnu.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD autolearn=disabled version=3.3.2 Received: from fencepost.gnu.org ([2001:4830:134:3::e]:58436) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d8QOJ-0006xl-Vj for control@debbugs.gnu.org; Wed, 10 May 2017 08:06:52 -0400 Received: from reverse-83.fdn.fr ([80.67.176.83]:33376 helo=ribbon) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1d8QOJ-0000Iv-CH for control@debbugs.gnu.org; Wed, 10 May 2017 08:06:51 -0400 Date: Wed, 10 May 2017 14:06:49 +0200 Message-Id: <87h90svrty.fsf@gnu.org> To: control@debbugs.gnu.org From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: control message for bug #25328 MIME-version: 1.0 Content-type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-Spam-Score: -5.0 (-----) X-Debbugs-Envelope-To: control 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: -5.0 (-----) tags 25328 unreproducible close 25328 From unknown Fri Jun 13 09:59:43 2025 Received: (at fakecontrol) by fakecontrolmessage; To: internal_control@debbugs.gnu.org From: Debbugs Internal Request Subject: Internal Control Message-Id: bug archived. Date: Thu, 08 Jun 2017 11:24:04 +0000 User-Agent: Fakemail v42.6.9 # This is a fake control message. # # The action: # bug archived. thanks # This fakemail brought to you by your local debbugs # administrator From debbugs-submit-bounces@debbugs.gnu.org Mon Nov 08 08:40:59 2021 Received: (at control) by debbugs.gnu.org; 8 Nov 2021 13:40:59 +0000 Received: from localhost ([127.0.0.1]:56850 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mk4tP-0001Md-Fq for submit@debbugs.gnu.org; Mon, 08 Nov 2021 08:40:59 -0500 Received: from mail-4018.proton.ch ([185.70.40.18]:38647) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mk4tN-0001MN-Jb for control@debbugs.gnu.org; Mon, 08 Nov 2021 08:40:58 -0500 Date: Mon, 08 Nov 2021 13:40:50 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lendvai.name; s=protonmail2; t=1636378851; bh=uEdCSpPttEBvUQH3z2iswn5kW43JrLuKHiiURvbmqj0=; h=Date:To:From:Reply-To:Subject:From; b=SUluZZm7Czvjecoa313laUdE0qRsPg4UFB9iiLlShaaegJzM8gXxP/oqgriTwNM81 dGzPipObqA4cqafBA7g2wP2DZ2G5X9sHkEY/Ep0Gx6DkfHv0w7Q/y3WZ2g5MzzWRR7 jmPxBIJ2RG41udrGwORsPSuL0daew1Q9CWpXwyffMS1op0g41xKAzbz9TTEVtzSlJI /S+uIHTHHS2CKXSJwjq0nLgiw/ubpFuiqHOos5tSyzO/Eedjv+GcIEA+7nbLLslN37 dCA+Y5CVGh4zp8D4oM+yNBs3UYjgR93oXsgs96vyLZmBxNRcQAsvLSqnijwdhrEY+n eRVpH6s0QaPcQ== To: "control@debbugs.gnu.org" From: Attila Lendvai Subject: (No Subject) Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="b1_IPswebwcqkSaVVVahO8yZrxOYZg2NuS6HLclbfO0c" X-Spam-Status: No, score=-1.2 required=10.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,HTML_MESSAGE,TVD_SPACE_RATIO shortcircuit=no autolearn=disabled version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on mailout.protonmail.ch X-Spam-Score: 2.0 (++) X-Spam-Report: Spam detection software, running on the system "debbugs.gnu.org", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: unarchive 25328 unarchive 25328 Content analysis details: (2.0 points, 10.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 2.0 SLIGHTLY_BAD_SUBJECT Subject contains something slightly spammy -0.0 SPF_PASS SPF: sender matches SPF record -0.0 RCVD_IN_MSPIKE_H4 RBL: Very Good reputation (+4) [185.70.40.18 listed in wl.mailspike.net] 0.0 SPF_HELO_NONE SPF: HELO does not publish an SPF Record 0.0 HTML_MESSAGE BODY: HTML included in message -0.0 RCVD_IN_MSPIKE_WL Mailspike good senders 0.0 TVD_SPACE_RATIO No description available. X-Debbugs-Envelope-To: control 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: , Reply-To: Attila Lendvai Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: 1.0 (+) This is a multi-part message in MIME format. --b1_IPswebwcqkSaVVVahO8yZrxOYZg2NuS6HLclbfO0c Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 dW5hcmNoaXZlIDI1MzI4 --b1_IPswebwcqkSaVVVahO8yZrxOYZg2NuS6HLclbfO0c Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: base64 PGRpdj48c3BhbiBzdHlsZT0iY29sb3I6IHJnYigzOCwgNDIsIDUxKTsgZm9udC1zdHlsZTogbm9y bWFsOyBmb250LXZhcmlhbnQtbGlnYXR1cmVzOiBub3JtYWw7IGZvbnQtdmFyaWFudC1jYXBzOiBu b3JtYWw7IGZvbnQtd2VpZ2h0OiA0MDA7IGxldHRlci1zcGFjaW5nOiBub3JtYWw7IG9ycGhhbnM6 IDI7IHRleHQtYWxpZ246IHN0YXJ0OyB0ZXh0LWluZGVudDogMHB4OyB0ZXh0LXRyYW5zZm9ybTog bm9uZTsgd2hpdGUtc3BhY2U6IHByZS13cmFwOyB3aWRvd3M6IDI7IHdvcmQtc3BhY2luZzogMHB4 OyAtd2Via2l0LXRleHQtc3Ryb2tlLXdpZHRoOiAwcHg7IGJhY2tncm91bmQtY29sb3I6IHJnYigy NTUsIDI1NSwgMjU1KTsgdGV4dC1kZWNvcmF0aW9uLXRoaWNrbmVzczogaW5pdGlhbDsgdGV4dC1k ZWNvcmF0aW9uLXN0eWxlOiBpbml0aWFsOyB0ZXh0LWRlY29yYXRpb24tY29sb3I6IGluaXRpYWw7 IGZsb2F0OiBub25lOyBkaXNwbGF5OiBpbmxpbmUgIWltcG9ydGFudDsiPjxzcGFuIGNsYXNzPSJm b250IiBzdHlsZT0iZm9udC1mYW1pbHk6U0ZNb25vLVJlZ3VsYXIsIENvbnNvbGFzLCAmcXVvdDtM aWJlcmF0aW9uIE1vbm8mcXVvdDssIE1lbmxvLCBtb25vc3BhY2UsIG1vbm9zcGFjZSI+PHNwYW4g Y2xhc3M9InNpemUiIHN0eWxlPSJmb250LXNpemU6MTcuNXB4Ij51bmFyY2hpdmUgMjUzMjg8L3Nw YW4+PC9zcGFuPjwvc3Bhbj48YnI+PC9kaXY+PGRpdiBjbGFzcz0icHJvdG9ubWFpbF9zaWduYXR1 cmVfYmxvY2siPjxkaXYgY2xhc3M9InByb3Rvbm1haWxfc2lnbmF0dXJlX2Jsb2NrLXByb3RvbiBw cm90b25tYWlsX3NpZ25hdHVyZV9ibG9jay1lbXB0eSI+PC9kaXY+PC9kaXY+PGRpdj48YnI+PC9k aXY+ --b1_IPswebwcqkSaVVVahO8yZrxOYZg2NuS6HLclbfO0c-- From unknown Fri Jun 13 09:59:43 2025 Received: (at fakecontrol) by fakecontrolmessage; To: internal_control@debbugs.gnu.org From: Debbugs Internal Request Subject: Internal Control Message-Id: bug archived. Date: Tue, 07 Dec 2021 12:24:05 +0000 User-Agent: Fakemail v42.6.9 # This is a fake control message. # # The action: # bug archived. thanks # This fakemail brought to you by your local debbugs # administrator