When I open an ascii armor encryptes textfile in the editor and klick on decrypt and enter the passphrase a window with an errormessage appears "Entschlüsselung fehlgeschlagen" (decryption failed). In the window there is a "Details" dialog. When I go on details and enlarge the window it contains the following: [GNUPG:] DECRYPTION_KEY 307DF5270E03CF60A318170B71880C73136CC2BE 6E2CEED78082C59F2F973CF05F6AB4482F2FA8AF u [GNUPG:] BEGIN_DECRYPTION [GNUPG:] DECRYPTION_COMPLIANCE_MODE 23 [GNUPG:] DECRYPTION_INFO 2 9 [GNUPG:] PLAINTEXT 62 1527437314 <here comes the decrypted cleartext of the file> [GNUPG:] DECRYPTION_OKAY [GNUPG:] GOODMDC [GNUPG:] END_DECRYPTION So allthough the file gets decrypted to its cleartext an errormessage comes up saying that there was an error. Also I can decrypt the file on the commandline using gpg without a problem. This bug seems to have appeared with version 18.04.1. Also Bug 336764 seems to have appeared with this release.
(In reply to Jens Stomber from comment #0) > When I open an ascii armor encryptes textfile in the editor and klick on > decrypt and enter the passphrase a window with an errormessage appears > "Entschlüsselung fehlgeschlagen" (decryption failed). In the window there is > a "Details" dialog. When I go on details and enlarge the window it contains > the following: > > [GNUPG:] DECRYPTION_KEY 307DF5270E03CF60A318170B71880C73136CC2BE > 6E2CEED78082C59F2F973CF05F6AB4482F2FA8AF u > [GNUPG:] BEGIN_DECRYPTION > [GNUPG:] DECRYPTION_COMPLIANCE_MODE 23 > [GNUPG:] DECRYPTION_INFO 2 9 > [GNUPG:] PLAINTEXT 62 1527437314 > <here comes the decrypted cleartext of the file> > [GNUPG:] DECRYPTION_OKAY > [GNUPG:] GOODMDC > [GNUPG:] END_DECRYPTION > > So allthough the file gets decrypted to its cleartext an errormessage comes > up saying that there was an error. Also I can decrypt the file on the > commandline using gpg without a problem. > > This bug seems to have appeared with version 18.04.1. Also Bug 336764 seems > to have appeared with this release. On archlinux with kgpg version 18.04.2 this bug has just disappeared. Everything is back to normal. Thank you for your support!