Bug 248239 - "All feeds" folder does not show new postings
Summary: "All feeds" folder does not show new postings
Status: RESOLVED UNMAINTAINED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: 1.6.5
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-18 13:40 UTC by hannes
Modified: 2017-01-07 21:58 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
OGG-Video: New messages not visible until "all fields" is left and re-selected (sorry for the bad quality). (527.13 KB, audio/ogg)
2010-08-18 13:40 UTC, hannes
Details

Note You need to log in before you can comment on or make changes to this bug.
Description hannes 2010-08-18 13:40:14 UTC
Created attachment 50696 [details]
OGG-Video: New messages not visible until "all fields" is left and re-selected (sorry for the bad quality).

Version:           1.6.5 (using KDE 4.5.0) 
OS:                Linux

When "All feeds" is the selected "folder" when a new posting is retrieved, it does not "reload" and show that new posting. It stays with the list of old (and read) messages.

In order to see the new one in "all feeds", I have to select another folder (i.e. subfolder of "all feeds") and then select "all feeds" again.

Reproducible: Always

Steps to Reproduce:
1) Select "all feeds"
2) Have new message retrieved

Actual Results:  
List of postings in "all feeds" does not change.

Expected Results:  
List of postings in "all feeds" should show the new message.

OS: Linux (x86_64) release 2.6.32-24-generic
Compiler: cc
Comment 1 Denis Kurz 2016-09-24 19:42:54 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 21:58:43 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.