RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1444073 - Folders do not show correct unread message count
Summary: Folders do not show correct unread message count
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: evolution
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Milan Crha
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-20 13:52 UTC by Milan Crha
Modified: 2017-08-01 12:27 UTC (History)
3 users (show)

Fixed In Version: evolution-3.22.6-10
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 12:27:11 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2066 0 normal SHIPPED_LIVE evolution bug fix and enhancement update 2017-08-01 16:05:58 UTC

Description Milan Crha 2017-04-20 13:52:01 UTC 
From Fedora bug #1440068, which I've accidentally reproduced in RHEL 7.4:

It can happen that folder tree on the left can only increase unread count, but not decrease.

Steps to reproduce (assumed there is configured an IMAPx account with GSSAPI authentication):
a) stop evolution
b) in terminal: kdestroy (there is no ticked for the account now)
c) run evolution
   * it shows an error message at the top that the ticket is missing and
     the folder tree shows only the account node with a connection error
     on the right of the account node
d) switch to a terminal and run: kinit (and fill credentials)
e) switch back to evolution and expand the account node
   * it loads properly now, folders are shown
f) select any folder from this account, where is at least one message
g) click in the icon column to mark one of the messages read or unread

While the count in the folder tree should increase when the message is marked as unread and decrease when it is marked read, it only increases the value when the messages is marked unread, but doesn't decrease the value when it is marked read. Having the ticket before start of evolution will make this behave as expected.

There is a patch for this in the Fedora bug, currently offered to the reporter for testing.
Comment 3 Bohdan Milar 2017-06-19 12:02:26 UTC 
Tested manually on x86_64 using evolution-3.22.6-10.el7

I used reproducer from Description. Folders did show correct unread message count while increase and even decrease.
Comment 4 errata-xmlrpc 2017-08-01 12:27:11 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2066
Note You need to log in before you can comment on or make changes to this bug.