Description of problem: If Fedora 27 and Fedora 28 I noticed Liferea would frequently hang. CPU utilization goes to 100% and program is unresponsive to mouse clicks or keyboard or screen refresh. Also does not respond to kill signals TERM, HUP or INT but does terminate on ILL and (of course -9). Was able to isolate it down to the "Next Unread" or "N" keyboard action when no more undread items were available. (I frequently would "N" to articles until it said "no unread items". Now it just dies and I have to kill it. Version-Release number of selected component (if applicable): 1.12.3 How reproducible: Reliable (for me). If there are 0 items unread and I hit N or hit the "Next Unread" button it dies. In fact, if I hit the next unread button, that button does not "ungray" at mouse release. Steps to Reproduce: 1. Load up a significant number of subscriptions (uncertain if this had an impact). 2. Browse through all unread items until there are 0. 3. Type N or hit "next unread. Actual results: Program is then unresponsive to mouse kicks, keyboard (Cntrl-Q), or window focus envents (leading to black screens). From a terminal screen, top indicates 100% CPU utilization. Program is unresponsive to most kill signals except ILL and KILL. Expected results: Program would continue to operate and often beings a refresh (note: Referesh All does not cause this failure. Only the Next Unread when there are 0). Additional info:
liferea-1.12.3-2.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-007d1ce119
liferea-1.12.3-2.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-007d1ce119
Updated and tested. Works as expected. +1 Many thanks!
liferea-1.12.3-2.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.