| Summary: | Creating a revocation certificate file fails silently | ||
|---|---|---|---|
| Product: | [Applications] kleopatra | Reporter: | piedro <piedro.kulman> |
| Component: | general | Assignee: | Andre Heinecke <aheinecke> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | fella, inb-bugzilla-1e1cff, mutz, piedro.kulman, pim-bugs-null, sz.szabolcs |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
piedro
2023-02-17 13:55:18 UTC
As of version 3.1.24.221202 (22.12.2) I can't reproduce your issue, however I recall a similar problem occurring with the Flatpak version of Kleopatra. If that is the case it's likely to be a permission issue. No, it's not flatpak but a fresh install of KDE openSUSE Tumbleweed.... I managed to reproduce the issue and found a workaround: kleopatra started from Konsole (terminal) can generate the revocation key. Version 3.1.28.240200 (24.02.0) openSUSE Tumbleweed 20240314 It seems like this is caused by starting kleopatra in KProcessRunner::SystemdAsService mode |