Version: 1.6.6 (using KDE 4.6.5) OS: Linux While the focus is on the feed, the new articles are added to an other position in the list and once they are read, the focus remains on the last read article. I've noticed this problem way back, so it has been affecting akragator versions at least throughout all 4.6 releases and probably earlier, too. Reproducible: Always Steps to Reproduce: 0. I keep my articles sorted according descending Date 1. Select a frequently updated site, e.g. major news organisation. I see this problem on http://www.bbc.co.uk/go/rss/int/news/-/news/ 2. Start reading the latest news by selecting Go/Next unread article. I press the + key to from one article to an other. 3. While you still have unread articles, stop all activities in akregator until new articles have been fetched. My akregator uses (the default) interval fetching every 30 minutes. 4. Later, resume pressing +. All the unred articles at top of the list will eventually be marked read. After these, the focus will move to the end of the list, where articles fetch while the feed was actively read have been collected. One could ask if that is the right way of dealing with new articles, but that is an other issue - I suppose? 5. When the last article in the list is read, pressing the + key does not move the focus anywhere. I have to move the focus by cursor to the an other feed. Actual Results: Focus was stuck until cursor was used to move it. Expected Results: Moved on to next feed. OS: Linux (x86_64) release 2.6.38-10-generic Compiler: gcc
This also appears in the 4.7.1 version. Some articles are completely hidden (left table shows unread articles, but the feed list contains no unread articles), you have to switch to another feed and switch back to this one. My default search order is new articles top.
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.
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.