Created attachment 154975 [details] Screenshot SUMMARY Fetched articles are sometimes put to wrong feed STEPS TO REPRODUCE 1. unknown, potentially this has something to do with unstable network 2. 3. OBSERVED RESULT Since recently I see that randomly some entries are in wrong feed. See the screenshot attached: it shows "asio" articles in "yaml-cpp" feed, and the "asio" feed shows broken icon instead of the usual feed favicon (of github in this case). If I just tell the broken feed (asio on the screenshot) to refresh, it successfully does so. But every time this happens I also need to clean the feed which received these articles. Whenever it breaks again, I see the notification about 10 new articles. I saw this happening not only with github feeds. This feels like some kind of race between different feeds starting the fetch and asynchronously getting the result or the error. EXPECTED RESULT Every article should be put to the correct place SOFTWARE/OS VERSIONS Linux/KDE Plasma: kernel 5.15.80-gentoo x86_64 (available in About System) KDE Plasma Version: 5.25.5 KDE Frameworks Version: kde-frameworks/plasma-5.99.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION
This has also happened to me today (2023-01-03). In my case it's the old Groklaw feed, that hasn't had new entries since 2013 (I've been carting around this same feed list for some time!). Twice today all the Groklaw articles have been added to another feed as unread, and not the same feed each time. The Groklaw feed was indeed showing an error (red cross icon) both times I noticed this. Operating System: Debian GNU/Linux KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.6 Kernel Version: 6.0.0-6-amd64 (64-bit)
(In reply to mel from comment #1) What's your Akregator version? that's separate 2 numbers from frameworks etc. Available in Help/About above the tabs
(In reply to Alexey Sokolov from comment #2) > What's your Akregator version? that's separate 2 numbers from frameworks > etc. Available in Help/About above the tabs Ah, good point! I'm using "5.21.3 (22.08.3)" of Akregator
This sounds like a duplicate of https://bugs.kde.org/show_bug.cgi?id=458116