From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?Q?=C3=93scar_Fuentes?= Subject: Re: org-crypt broken on Ubuntu 18.04 Date: Wed, 20 Jun 2018 04:05:45 +0200 Message-ID: <87bmc6civa.fsf@telefonica.net> References: <87bmceeh0x.fsf@telefonica.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:60413) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fVSVS-0003sA-6U for emacs-orgmode@gnu.org; Tue, 19 Jun 2018 22:05:59 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fVSVO-0007Ax-Vy for emacs-orgmode@gnu.org; Tue, 19 Jun 2018 22:05:58 -0400 Received: from [195.159.176.226] (port=58636 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fVSVO-00079g-ON for emacs-orgmode@gnu.org; Tue, 19 Jun 2018 22:05:54 -0400 Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1fVSTF-0000aD-Dl for emacs-orgmode@gnu.org; Wed, 20 Jun 2018 04:03:41 +0200 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org Óscar Fuentes writes: > Hello. > > Today I noticed that org-crypt is broken on my daily driver. > > On a header with the :crypt: tag I invoke org-decrypt-entry, a popup > dialog asks for the password, I type the password and then the > minibuffer shows > > GPG error: "Decryption failed", "" > > The complete error message on *Messages* is > > epg--check-error-for-decrypt: GPG error: "Decryption failed", "" > > This is a very recent problem. In dpkg.log I see: > > 2018-06-12 00:33:00 upgrade gnupg-utils:amd64 2.2.4-1ubuntu1 2.2.4-1ubuntu1.1 > > 2018-06-12 00:33:05 upgrade gnupg:amd64 2.2.4-1ubuntu1 2.2.4-1ubuntu1.1 > > I tried the latest org-mode (9.1.13) and Emacs from master branch but > the problem persists. Today I upgraded a Debian Testing machine which included gpg 2.2.8 and, sure enough, now that machine also presents the same problem. I'll try to debug the issue as soon as I have some spare time.