From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Daniel Semyonov via "Bug reports for GNU Emacs, the Swiss army knife of text editors" Newsgroups: gmane.emacs.bugs Subject: bug#64789: 30.0.50; EPA fails to encrypt files; decryption and manual encryption works Date: Sat, 22 Jul 2023 16:23:05 +0300 Message-ID: <87pm4km66e.fsf@dsemy.com> References: <87wmysmgf1.fsf@dsemy.com> <83tttw891n.fsf@gnu.org> Reply-To: Daniel Semyonov Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="29969"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: 64789@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Jul 22 15:26:36 2023 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qNCd2-0007Ya-5Q for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 22 Jul 2023 15:26:36 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qNCco-0003Tr-OR; Sat, 22 Jul 2023 09:26:22 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qNCci-0003Se-47 for bug-gnu-emacs@gnu.org; Sat, 22 Jul 2023 09:26:16 -0400 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1qNCcU-0008Ob-7Z for bug-gnu-emacs@gnu.org; Sat, 22 Jul 2023 09:26:12 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1qNCcU-0006VY-2C for bug-gnu-emacs@gnu.org; Sat, 22 Jul 2023 09:26:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Daniel Semyonov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 22 Jul 2023 13:26:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 64789 X-GNU-PR-Package: emacs Original-Received: via spool by 64789-submit@debbugs.gnu.org id=B64789.169003235225000 (code B ref 64789); Sat, 22 Jul 2023 13:26:02 +0000 Original-Received: (at 64789) by debbugs.gnu.org; 22 Jul 2023 13:25:52 +0000 Original-Received: from localhost ([127.0.0.1]:35671 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qNCcJ-0006V9-IE for submit@debbugs.gnu.org; Sat, 22 Jul 2023 09:25:51 -0400 Original-Received: from dsemy.com ([46.23.89.208]:27458) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qNCcH-0006Uw-Ld for 64789@debbugs.gnu.org; Sat, 22 Jul 2023 09:25:50 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; s=dkim; bh=fZgfpxVdWObd5 QDQOcmwrT9QNyDVP+79YXGfo11O3aM=; h=date:references:in-reply-to: subject:cc:to:from; d=dsemy.com; b=H950UJbHvKzJpLhOIqzagdUN0fza5G3hu7f LC1NGL1rEMKIOfzJ+vSwblFQvL51/achbxU6Q8Sq2gOcGy8jtAHabdQGxyGlMKcoN7hAde Q73StWkb0G9wKRh9n52MHsj+so+6pM850f+lFs/UqtvZA2/zYx2rZL9voYFTngXEnOfEf/ bzEJKJhVRqm3Ilvdez8o4PgFRtwEhUnqzhyrHsyD5yIDlWhD7qv7t3YUKa5xQsnaaVW3aL Gdumx5dulM/NeddOXwrt77J77MjGtW0r2fFakGw65YSDkcxJCf7vA6OpxKXnbJqBDZa789 L0RzFDl8mfVCPrkFLtaj/qKMxlQ== Original-Received: from coldharbour.home.arpa ( [147.235.213.12]) by dsemy.com (OpenSMTPD) with ESMTPSA id 24544c83 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Sat, 22 Jul 2023 15:25:43 +0200 (CEST) Original-Received: from localhost (coldharbour.home.arpa [local]) by coldharbour.home.arpa (OpenSMTPD) with ESMTPA id a04d4498; Sat, 22 Jul 2023 13:23:05 +0000 (UTC) In-Reply-To: <83tttw891n.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 22 Jul 2023 14:44:52 +0300") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:265811 Archived-At: >>>>> Eli Zaretskii writes: >> Date: Sat, 22 Jul 2023 12:41:54 +0300 From: Daniel Semyonov via >> "Bug reports for GNU Emacs, the Swiss army knife of text editors" >> >> >> >> For the past few days I've noticed I can no longer encrypt files >> with EPA, both new files which I save with a '.gpg' extension and >> choose a recipient, or existing files which are successfully >> decrypted but I can't modify and save. Specifically, when >> attempting to save, EPA just gets stuck indefinitely with "Saving >> file .gpg..." in the echo area. >> >> AFAIK my GPG config hasn't changed in months (and I fairly >> recently encrypted a file with EPA), and I can manually invoke it >> to encrypt files (through the terminal or dired for example). I >> also got an error yesterday when trying to encrypt a file through >> dired (by pressing '!' on the file and typing the command) which >> said something about GPG not finding a valid TTY, but I don't >> remember what it was and I can't reproduce it now. >> >> To reproduce failure to save an existing file: 1. $ emacs -Q >> 2. C-x C-f .gpg 3. Toggle buffer modified by clicking >> the indicator on the mode line. 4. C-x C-s 5. Wait forever. >> >> To reproduce failure to save a new file: 1. $ emacs -Q 2. C-x C-f >> .gpg 3. Toggle buffer modified by clicking the >> indicator on the mode line. 4. C-x C-s 5. Mark a recipient and >> press [OK]. 6. Wait forever. > This is due to a change in the latest version of GnuPG. We have > this in etc/PROBLEMS: > *** Saving, via EasyPG, a file encrypted with GnuPG hangs > This is known to happen with GnuPG v2.4.1. The only known > workaround is to downgrade to a version of GnuPG older than 2.4.1 > (or, in the future, upgrade to a newer version which solves the > problem, when such a fixed version becomes available). This is likely the issue, my distro seems to have upgraded from GnuPG 2.4.0 to 2.4.3 two weeks ago, I must have missed it when updating. Should I close the report, or maybe it makes sense to keep it open until a fixed version of GnuPG is released? Thanks, Daniel