Bug 353833 - Akregator hangs when left open over time
Summary: Akregator hangs when left open over time
Status: RESOLVED UNMAINTAINED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Kubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-12 19:01 UTC by James Cain
Modified: 2018-02-01 09:48 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 James Cain 2015-10-12 19:01:32 UTC
Whenever Akregator is left running for an unspecified period of time, it will eventually hang and become unresponsive. The application window will get an unresponsive message and ask if I want to terminate the app. When finished, Akregator can then be restarted and will work properly until it hangs again.

Reproducible: Always

Steps to Reproduce:
1. Open Akregator
2. Minimize and continue working on the computer
3. Open Akregator window from panel and screen will be white and app. is unresponsive. 

Actual Results:  
The application must be restarted to work properly, until it hangs again.

Expected Results:  
No hang-ups.

Not sure if it is related to a particular feed. I will remove all feeds and add back one by one to see if there is any correlation between a particular feed and the app hanging up. Also, it is unclear what debug symbols should be installed, as issuing the command "apt-cache depends k3b | grep Suggests" reports nothing.
Comment 1 James Cain 2015-10-12 19:02:50 UTC
Akregator version: 4.14.7
Kubuntu 15.04
Plasma versin: 5.3.2
Comment 2 James Cain 2015-10-12 19:04:04 UTC
Make that above apt search command "apt-cache depends akregator | grep Suggests". But you get the idea.
Comment 3 Denis Kurz 2017-06-23 20:16:31 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 4 Denis Kurz 2018-02-01 09:48:39 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.