Bug 349700

Summary:	Showing the wrong preview of the feed's content
Product:	[Applications] akregator	Reporter:	Niklas Reitz <niklas.reitz>
Component:	feed parser	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Kubuntu
OS:	Linux
URL:	http://www.bilder-upload.eu/show.php?file=747084-1435524443.png http://www.bilder-upload.eu/show.php?file=4b5744-1435524501.png http://www.bilder-upload.eu/show.php?file=59609a-1435524520.png
Latest Commit:		Version Fixed In:

Description Niklas Reitz 2015-06-28 20:48:05 UTC

Akregator sometimes shows the wrong preview of the content of the selected article. That only appears on several feeds from a forum. Some previews include a recurrent text which wasn't part of a feed but was a comment of a post, i didn't subscribe.  An admistrator of the forum couldn't repoduce this error so it must be a problem with akregator

Reproducible: Sometimes

Steps to Reproduce:
1. subscribe http://www.android-hilfe.de/forum/android-allgemein.20/index.rss
2. select a post to see the preview
3. You will often see a preview with the same content (it's german)

Actual Results:  
wrong content: "Hm, aber in welche Partition sollte ich das denn flashen? Das "flash" command erwartet ja eine Partition. Eine /Boot gibts doch gar nicht oder?
Erase klappt übrigens nicht (remote not allowed), brauch also wirklich den ENG Bootloader.
EDIT: Na super, die PC10IMG.zip flashen geht auch..."

Expected Results:  
right content

Using Kubuntu 15.04 with Akregator 4.14.6.

Comment 1 Denis Kurz 2017-06-23 19:58:21 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:49:48 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.