Bug 351547

Summary:	Akregator5 crashes with websites opened
Product:	[Applications] akregator	Reporter:	Robby Engelmann <robby.engelmann>
Component:	internal browser	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	bugs.kde.org, flateric, robby.engelmann, tomas.nackaerts
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Robby Engelmann 2015-08-21 05:32:09 UTC

Akregator5 (under 15.07.90 and 15.08.0) is crashing when opened sites in tabs and then is also crashing Kontact5. Drkonqi is not triggered, whole Kontact5 simply closes.


Reproducible: Always

Steps to Reproduce:
1. open Kontact5, switch to Akregator5
2. update Feeds, open a random new feed in a new tab
3. switch to another program opened, e.g. firefox
4. search for a solution of another 15.08.0 problem
5. try to read opened tab in Akregator5 --> hmm, it not there anymore :-)



using openSUSE tumbleweed with lastest snapshot installed and Repo for Factory_Apps_standard and Frameworks5_factory repos.

Comment 1 HT 2015-08-31 08:46:50 UTC

Same problem on Archlinux with clean profile. I'm using only Akregator5 without Kcontact. Open link in internal browser cause aplication crash. Restoring previous sessions cause another crash.

Plasma: 5.4.0
Akregator: 15.08.0
QT version:  5.5.0

Comment 2 Robby Engelmann 2015-09-24 14:08:43 UTC

*** Bug 352784 has been marked as a duplicate of this bug. ***

Comment 3 Robby Engelmann 2015-10-28 06:08:02 UTC

Still valid for me under Qt 5.5.1, Plasma 5.4.2, KF 5.15 and KDE Apps 15.08.2

Comment 4 m.eik michalke 2016-11-07 10:21:20 UTC

i think i'm running into the same or a very similar crash (akregator 15.12.3, kubuntu 16.04 with kde-backports PPA). akregator reproducibly crashes itself and all of kontact when i try to read certain entries of the RWeekly.org feed (https://rweekly.org/atom.xml), e.g. issue 24. it's not all issues of this feed, but happens every once in a while.

given that there's also a duplicate of this bug, it should be classified as "CONFIRMED".