| Summary: |
Deselecting Signing check box in Advanced Settings - Certificate Usage results in General Error in Kleopatra |
| Product: |
[Applications] kleopatra
|
Reporter: |
Niall <niall.guerin> |
| Component: |
general | Assignee: |
Andre Heinecke <aheinecke> |
| Status: |
CONFIRMED
---
|
|
|
| Severity: |
normal
|
CC: |
kdepim-bugs, luke1410, mutz
|
| Priority: |
NOR
|
|
|
| Version: |
2.3.0 | |
|
| Target Milestone: |
--- | |
|
| Platform: |
Microsoft Windows | |
|
| OS: |
Microsoft Windows | |
|
|
Latest Commit:
|
|
Version Fixed In:
|
|
|---|
|
Sentry Crash Report:
|
|
| |
|---|
| Attachments: |
Kleopatra Version 2.3.1 - Steps to Reproduce
|
Created attachment 99024 [details] Kleopatra Version 2.3.1 - Steps to Reproduce If using Kleopatra on Windows 10 operating system and following standard use case of File - New Certificate, select Create a Personal OpenPGP... option. Fill in the Name, EMail, and leave Comment field blank. Click Advanced Settings button. Go with defaults, but deselect the Signing checkbox as that checkbox is optional in UI. Click Create Key. Result: Could not create certificate: General Error. Retests: tested this with data in Comment field and without data in case any entry I made was impacting the checkbox activity in parallel. Also tested making changes to Date expiry and leaving at default. If I reselect the Signing checkbox, the certificate creation process runs fine as normal, so just that checkbox being deselected results in error. GPG4Win install is fine otherwise and all other functions I need for now are executing fine both from Kleopatra and command line windows. I was testing this after running some tests in the command-line utility for creation of separate sign-only certificates, so came across more by accident as I would not normally deselect the Signing option when creating a New cert in Kleopatra. I had checked the Bug database for older bugs and autolist when logging this but not seeing a duplicate. Please discard if it is and sorry for the noise it is a duplicate of an old bug. I ran a test on two other versions as I initially thought it was the 2.3.1 version I installed today and that 2.3.1 was the problem, but it wasn't as using Signing option everything works fine. I noticed the same error behavior in the 2.3.0 release and the original older version I had: 2.2.6. Everything was tested on Windows 10. I have attached a document with 2 screenshots illustrating precondition and failed cert creation result.