After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 574224 - Evolution Mail and Calendar: evolution-rss. viewing ...
Evolution Mail and Calendar: evolution-rss. viewing ...
Status: RESOLVED OBSOLETE
Product: evolution-rss
Classification: Other
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: evolution-rss-maint
evolution-rss-maint
Depends on:
Blocks:
 
 
Reported: 2009-03-05 08:13 UTC by jo3
Modified: 2021-05-25 12:36 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description jo3 2009-03-05 08:13:12 UTC
evolution-rss.  viewing and closing the last unread rss item regardless of the order in which feeds are selected does not set the last feed's unread count to 0, it remains 1.  While no messages are unread in whichever folder that is, the folder is still bold and shows (1).

work around: select that folder, mark any message as unread, then mark it as unread.


Distribution: Fedora release 10 (Cambridge)
Gnome Release: 2.24.3 2009-01-16 (Red Hat, Inc)
BugBuddy Version: 2.24.2
Comment 1 Lucian Langa 2009-03-05 18:30:29 UTC
Hmm... I cannot reproduce this in any way.
Can you detail this process?
Is it possible you could also send a screen shot of your feed folders ?
Is it possible you see this problem on normal evolution mail folders too ?
Comment 2 Alexander Usyskin 2009-07-10 18:15:15 UTC
Look like that I have the close problem:
After selecting "Mark all items as read" sometimes feed folder lists (1) in unread count and stays bold, but all feed items marked as read.
Workaround is same: mark one item as unread and read it.
I don't have this problem on normal mail folders.

Distribution: Ubuntu Jaunty Jackalope 9.04
Gnome: 2.26.1
evolution-rss: 0.1.2

Comment 3 André Klapper 2021-05-25 12:36:50 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new enhancement request ticket at
  https://gitlab.gnome.org/GNOME/evolution-rss/-/issues/

Thank you for your understanding and your help.