Bug 285102 - akregator hangs or freezes on selecting unread slashdot rss item
Summary: akregator hangs or freezes on selecting unread slashdot rss item
Status: RESOLVED UNMAINTAINED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: 1.6.6
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-27 15:15 UTC by hinsch.martin
Modified: 2017-01-07 22:06 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description hinsch.martin 2011-10-27 15:15:32 UTC
Version:           1.6.6 (using KDE 4.7.2) 
OS:                Linux

After the first unread item in the Slashdot rss has been selected Akregator hangs. The unread item displays fine but the application becomes unresponsive. Sometimes it unfreezes after half a minute or so, sometimes it seems to be stuck forever. In some cases a waiting cursor is shown. 
I have plenty of feeds in my akregator but Slashdot is the only one that triggers this behaviour. I tried removing and re-adding the feed but that doesn't change anything.

Reproducible: Always

Steps to Reproduce:
Wait for an unread item to appear in the slashdot feed, select it by mouse or keyboard.

Actual Results:  
Akregator becomes unresponsive, sometimes with waiting cursor.

Expected Results:  
this shouldn't happen.

OS: Linux (x86_64) release 2.6.38-12-generic
Compiler: gcc
Comment 1 Denis Kurz 2016-09-24 19:40:35 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of akregator (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 22:06:30 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.