Bug 341839 - No hint why i cannot select a s/mime certificate for signing or encryption
Summary: No hint why i cannot select a s/mime certificate for signing or encryption
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: crypto (show other bugs)
Version: 4.14.2
Platform: Arch Linux Linux
: NOR minor
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-13 10:42 UTC by Erik
Modified: 2018-01-31 16:54 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Erik 2014-12-13 10:42:42 UTC
I am trying to add a s/mime certificate to one of my identities. I have imported it using kleopatra but something went wrong (which I am still trying to narrow down). But meanwhile I see another problem connected to this:

The dialog, where I can select a s/mime certificate for signing or encryption, shows the certificate I have imported before. But once I select it, the icon in the 'Key ID' column gets a red cross indicating some kind of problem. But the dialog does not give any kind of hint what is actually wrong. 

It would be nice to have some kind of error message (maybe as a tooltip on the red cross of the icon, maybe displayed somewhere in the dialog).

Reproducible: Always

Steps to Reproduce:
1. Edit identity
2. Cryptography: change s/mime signing certificate or change s/mime encryption certificate
3. Select a bad certificate is the selection dialog

Actual Results:  
Red cross in the 'Key ID' column, no error message, 'Ok' button is disabled.

Expected Results:  
Give some kind of error message (displayed as tooltip or within the dialog window) which helps the user to track down the problem.

I am in two minds whether this a bug or a feature request. In its core, I suggest a kind of a new feature (some kind of error message in case of problems with one of the certificates). But on the other hand, the current behavior can be quite frustrating for the average user, because there is clearly something going wrong but there is no helpful information displayed. So there is clearly something missing and therefore I have select 'minor bug' for this.
Comment 1 Denis Kurz 2017-06-23 19:57:42 UTC
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 2 Denis Kurz 2018-01-31 16:54:19 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12, preferably more recent), please open a new one unless it already exists. Thank you for all your input.