Bug 246415 - Updated feeds do not show in right pane
Summary: Updated feeds do not show in right pane
Status: RESOLVED UNMAINTAINED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: 1.6.2
Platform: Unlisted Binaries Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-01 13:26 UTC by jwreese0
Modified: 2017-01-07 21:41 UTC (History)
2 users (show)

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 jwreese0 2010-08-01 13:26:41 UTC
Version:           1.6.2
OS:                Linux

Feeds appear to update normally in the left pane, but new articles do not show up in either one of the right panes. Feeds are set to update upon opening Akregator, and this continues to operate normally. The upper right pane shows old articles but no articles that have been downloaded since the bug first appeared.

Reproducible: Always

Steps to Reproduce:
Open Akregator, wait for Akregator to refresh feeds (usually about ten seconds).

Actual Results:  
The left pane increments the number of articles available for each feed by the number of articles that have just been downloaded. The upper right pane does not have any new articles; old articles appear there, and they all precede the date that this bug first appeared. The old articles can still be opened in the lower right pane.

Expected Results:  
Left pane incremented the number of articles present to reflect the articles that have been downloaded in that session. New articles appear in upper right pane and can be opened in the lower right pane.

OS: Linux (i686) release 2.6.32-24-generic
Compiler: cc
Comment 1 Johan Erlands 2010-10-27 10:24:22 UTC
I have the same problem on 1.6.5.
Comment 2 Johan Erlands 2010-10-27 10:34:01 UTC
I think this is a duplicate of 206331.
Comment 3 Johan Erlands 2010-10-27 10:35:04 UTC
(In reply to comment #2)
> I think this is a duplicate of 206331.

https://bugs.kde.org/show_bug.cgi?id=206331
Comment 4 blobbyjj 2013-05-02 16:13:51 UTC
(In reply to comment #3)
> (In reply to comment #2)
> > I think this is a duplicate of 206331.
> 
> https://bugs.kde.org/show_bug.cgi?id=206331

I do not think this is a duplicate because of the fact the messages do not show up if one switches to another feed.

> So I selected other feed and then got back to feed A -- this time akregator shown 2 new messages at top of the list.

I have this problem with Kubuntu 13.04 so I wonder if there are any news. At the moment I can not use Akregator.
Comment 5 jwreese0 2013-05-03 10:38:59 UTC
Make sure there is no text in the 'search' field. That turned out to be
my problem. However, that does not appear to be your issue.



On Thu, 2013-05-02 at 16:13 +0000, blobbyjj@ymail.com wrote:
> https://bugs.kde.org/show_bug.cgi?id=246415
> 
> blobbyjj@ymail.com changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |blobbyjj@ymail.com
> 
> --- Comment #4 from blobbyjj@ymail.com ---
> (In reply to comment #3)
> > (In reply to comment #2)
> > > I think this is a duplicate of 206331.
> > 
> > https://bugs.kde.org/show_bug.cgi?id=206331
> 
> I do not think this is a duplicate because of the fact the messages do not show
> up if one switches to another feed.
> 
> > So I selected other feed and then got back to feed A -- this time akregator shown 2 new messages at top of the list.
> 
> I have this problem with Kubuntu 13.04 so I wonder if there are any news. At
> the moment I can not use Akregator.
>
Comment 6 Denis Kurz 2016-09-24 19:40:37 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 7 Denis Kurz 2017-01-07 21:41:36 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.