Bug 241866 - RSS feed got a "second batch" of feeds that were marked new BUT didn't change the count of new feeds
Summary: RSS feed got a "second batch" of feeds that were marked new BUT didn't change...
Status: RESOLVED WORKSFORME
Alias: None
Product: akregator
Classification: Applications
Component: kontact plugin (show other bugs)
Version: 1.6.2
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2010-06-16 00:08 UTC by Piotr
Modified: 2018-10-21 04:32 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
First batch just after subscribing to the RSS feed (132.44 KB, image/png)
2010-06-16 00:10 UTC, Piotr
Details
The "second batch" of feeds after "Fetch all feeds" (217.45 KB, image/png)
2010-06-16 00:11 UTC, Piotr
Details
Highlighted feed doesn't change it's status (146.68 KB, image/png)
2010-06-16 00:12 UTC, Piotr
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Piotr 2010-06-16 00:08:38 UTC
Version:           1.6.2 (using KDE 4.4.3) 
OS:                Linux

I recently subscribed to a feed (my.opera.com/desktopteam/blog/). After adding it immediately downloaded first 10 feeds, when i clicked to fetch all feeds it downloaded "second batch" (that was older) for the above RSS feed. The older feeds were marked as unread, they didn't change their status to read when i read them (actually i couldn't read them since nothing was even showing, highlighting the "first batch" showed normally the feed in the window below. Marking the "second batch" (older feeds) as read didn't work, they stayed as unread all the time. If i highlighted only once one of the "second batch" and then clicked All feeds Kontact was crashing if on the other hand after the "second batch" i didn't click it at all it didn't crash when clicking "All feeds" . That was reproducible every time i tried that. I can't reproduce it since i manually deleted that feed. 

Reproducible: Didn't try

Steps to Reproduce:
1.Subscribe to a feed (not every behaves like that?)
2.After downloading the feeds for the first time download them once again 
3.Some older feeds will appear as unread and they will not count as unread.

Actual Results:  
Feeds are marked as unread and do not update the "Unread" counter. Clicking that "malicious" feed and then clicking "All feeds" crashes Kontact

Expected Results:  
1. Those feeds shouldn't download at all
               OR
2. They should update the counter and be able to change the status to read after highlighting them
Comment 1 Piotr 2010-06-16 00:10:14 UTC
Created attachment 48047 [details]
First batch just after subscribing to the RSS feed

First batch of downloaded feeds just after subscribing to it.
Comment 2 Piotr 2010-06-16 00:11:36 UTC
Created attachment 48048 [details]
The "second batch" of feeds after "Fetch all feeds"

"Second batch" of feeds showing up after fetching again
Comment 3 Piotr 2010-06-16 00:12:08 UTC
Created attachment 48049 [details]
Highlighted feed doesn't change it's status
Comment 4 Piotr 2010-06-16 00:23:24 UTC
I can once again reproduce the weird behavior. Now i noticed that after the "second batch" if i don't click it and go to "All feeds" nothing happens BUT if i go back to that feed all those unaccounted unread feeds are gone and they will appear again if i only fetch them again.
Comment 5 Nicolas L. 2010-08-12 20:31:34 UTC
please add the backtrace of the crash on this bugreport.

http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
Comment 6 Andrew Crouthamel 2018-09-20 22:08:57 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Andrew Crouthamel 2018-10-21 04:32:58 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!