Bug 384013

Summary:	Kleopatra does not save revocation certificate
Product:	[Applications] kleopatra	Reporter:	Germano Massullo <germano.massullo>
Component:	general	Assignee:	Andre Heinecke <aheinecke>
Status:	CONFIRMED ---
Severity:	major	CC:	eloquence, kdepim-bugs, mutz, publi852159, t.rother
Priority:	NOR
Version:	3.1.1
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Germano Massullo 2017-08-25 16:44:54 UTC

Everytime I try to create a revocation certificate in a certain directory, it is empty because Kleopatra has not saved anything in it.
kleopatra-17.04.1

Comment 1 Thomas Rother 2019-06-19 06:21:35 UTC

confirmed for latest opensuse leap 15.1 
and kleopatra 3.1.3 (framework 5..55.0, qt 5.9.7)

Comment 2 publi852159 2020-10-20 23:07:00 UTC

revocation key is not generated, or not saved on external disks, in debian testing with version 3.1.11

Comment 3 Erik Moeller 2022-08-16 17:17:26 UTC

I'm seeing the same behavior in version 3.1.11 (the version included in current Tails OS). It appears to be related to how the `gpg` operations are performed; if I run Kleopatra from a terminal, I can save the revocation successfully (and see the `gpg` output in the terminal); if I run it without a TTY, I also cannot save successfully.