Bug 348948 - Server authentication failed - Popup keeps coming up after "Cancel"
Summary: Server authentication failed - Popup keeps coming up after "Cancel"
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-10 00:56 UTC by Christoph Herrmann
Modified: 2018-02-01 09:47 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 Christoph Herrmann 2015-06-10 00:56:09 UTC
Hi guys,

this is similar to bug 347497, but more general. If a certificate check fails on any resource, it seems I have no option but to "Continue" in some shape or form or have this annoying popup stay around for ever. (At least the Google Contacts does).

In other words, it warns me that something unsafe is about to happen but FORCES me to do it anyway. 

A "cancel" on such a dialog should shut down the resource (and possibly move the popup into the fancy notifications tray) so that I am not eventually give up and accept it!

Thank you and keep up the brilliant work!

Chris

Reproducible: Always

Steps to Reproduce:
1. Force a certificate error
2. Click cancel
3. Popup comes up again

Actual Results:  
Popup comes up again

Expected Results:  
Shut down the resource & shut up
Comment 1 Denis Kurz 2017-06-23 20:05:19 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-02-01 09:47:22 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 much more recent), please open a new one unless it already exists. Thank you for all your input.