Bug 351486

Summary:	Crashes after displaying Server Authenticity check failed
Product:	[Applications] akregator	Reporter:	clivejo <clivejo>
Component:	akregator konqueror plugin	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	montel, oliviervdtoorn
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Kubuntu
OS:	Linux
URL:	http://s22.postimg.org/i7yvsrdi9/Kontact_Crash.jpg
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description clivejo 2015-08-19 15:32:38 UTC

When trying to read the full story Kontact displays a warning message saying "The server failed the authenticity check (edge.quantserve.com)"  "The certificate does not apply to the given host"

Clicking either Continue or Cancel results in a crash of Kontact, which will loop if you Restore your session


Reproducible: Always

Steps to Reproduce:
1. Open Feeds
2. Navigate to KDE > Linux.com > Canonical's IP Policy Is Deliberately Vague, Says Matthew Garrett
3. Click on Complete Story
4. Click on Continue

Actual Results:  
Kontact crashes

Expected Results:  
The Complete Story should be displayed

Kubuntu Wily + KDE Apps 15.07.90

Comment 1 Olivier van der Toorn 2015-08-19 19:38:57 UTC

I can confirm this bug

Comment 2 Laurent Montel 2015-08-20 05:26:53 UTC

I need version
I need backtrace

Comment 3 Olivier van der Toorn 2015-08-20 06:45:00 UTC

I'm running Kontact 4.81 beta1. Checking this bug today the behaviour was somewhat different from yesterday. Clicking on the complete story button pops up a window about the certificate. Yesterday when I pressed details it crashed immediately. Today I get to see the details pane, then it crashes after a while. Just tested leaving the certificate pop up open, Kontact crashes after a while. 

Strange thing is DrKonqi doesn't show after the crash. Is there another way I can get you the backtrace?

Comment 4 Denis Kurz 2017-06-23 20:19:53 UTC

This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.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 opportunity 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 5 Denis Kurz 2018-02-01 09:53:12 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.