GNOME Bugzilla – Bug 355007
unread news article indicators out of sync
Last modified: 2019-11-12 19:11:21 UTC
Please describe the problem: This is minor but makes me crazy after a while. In a newsgroup account, I'll constantly see the group name highlighted in bold with a number of unread articles in parens after it, but if I click on the group, the summary that appears at the top of the sidebar will correctly indicate no unread articles. I'll have to do a send/recieve to get the group name back to normal non-bold, no unread article state. Steps to reproduce: 1. Create a news account on a nntp server with fairly low traffic. 2. Read news in a group that has some unread articles 3. Mark all article read 4. Hide read articles 5. See the newsgroup name in the sidebar indicating no unread articles 6. Click on different folder in sidebar to show something else in main window 7. Click on send/recieve 8. See the newsgroup name show up again with N unread articles 9. Click on the group name to go back there again 10. See the group having no unread articles, but the group name still bold. 11. Click on send/recieve one extra time 12. See the group name go back to all read state. Actual results: See above Expected results: Clicking send/recieve shouldn't make the group name go bold and tell me there are unread articles when, in fact, there are no unread articles. Does this happen every time? Yes. Other information: It acts a lot like the group name highlighting is somehow remembering what the count of unread articles was the last time we were there, not what it is based on the newest data obtained by send/recieve. The giveaway that this is an evolution bug and not a news server problem is the summary info for the group that appears at the top of the sidebar when you click on the group name. The summary correctly says nothing about unread articles, yet the group name down below is still bold and claims there are unread articles.
@devs: could it be a bug like what was happening with local inbox that (iirc) ross fixed some months ago ?
This version is no longer maintained, which means that it will not receive any further security or bug fix updates. The current stable GNOME and Evolution version is 2.26. Can you please check again whether this issue still happens in Evolution 2.24 or 2.26 and update this report by adding a comment and changing the "Version" field? Thanks a lot. Again thank you for reporting this bug and we are sorry it could not be fixed for the version you originally used here. Without feedback this report will be closed as INCOMPLETE in 6 weeks.
Thanks for taking the time to report this bug; however, closing due to lack of response of the reporter, sorry. if you still see this issue with a current release of evolution (2.26.3 or 2.28.x or later), please reopen. thanks in advance.
Confirming this is still an issue in 2.28.
With 2.24+ it's rather common even for other providers, though NNTP was earlier. I guess bug #553405 should cover this too, but I'm keeping this open as a special case.
Anyone knows whether this still happens in 3.26 or 3.24? Asking as lots of code has changed in the meantime.
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment. Thanks!