[kgpg] [Bug 394754] Unable to encrypt / decrypt / sign files in the editor

2018-06-07 Thread Jens Stomber
https://bugs.kde.org/show_bug.cgi?id=394754

--- Comment #1 from Jens Stomber  ---
(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 
> 
> [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!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kgpg] [Bug 336764] sign/verify in editor yields an error after key selection

2018-06-07 Thread Jens Stomber
https://bugs.kde.org/show_bug.cgi?id=336764

--- Comment #7 from Jens Stomber  ---
(In reply to Rolf Eike Beer from comment #6)
> Can you please try with the most recent version from the Applicatons/18.04
> branch? There was a bug in 18.04.1 that has already been fixed and we would
> like to rule out that this is just another manifestation of it.

On archlinux with kgpg version 18.04.2 this bug has just disappeared.
Everything is back to normal. Thank you for your support!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kgpg] [Bug 394754] New: Unable to encrypt / decrypt / sign files in the editor

2018-05-27 Thread Jens Stomber
https://bugs.kde.org/show_bug.cgi?id=394754

Bug ID: 394754
   Summary: Unable to encrypt / decrypt / sign files in the editor
   Product: kgpg
   Version: 18.04.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@opensource.sf-tec.de
  Reporter: jens.stom...@mailbox.org
  Target Milestone: ---

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 

[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.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kgpg] [Bug 336764] sign/verify in editor yields an error after key selection

2018-05-27 Thread Jens Stomber
https://bugs.kde.org/show_bug.cgi?id=336764

Jens Stomber <jens.stom...@mailbox.org> changed:

   What|Removed |Added

   Platform|Fedora RPMs |Archlinux Packages
 CC||jens.stom...@mailbox.org
Version|2.11|18.04.1

--- Comment #5 from Jens Stomber <jens.stom...@mailbox.org> ---
(In reply to Kavinda from comment #4)
> I couldn't reproduce this bug. Is this still an issue?

I can reproduce this bug on Archlinux with kgpg version 18.04.1. It seems that
the issue has appeared with this version.

-- 
You are receiving this mail because:
You are watching all bug changes.