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 1070764 - mark messages as read set to 0 leads to occasional read mark skip
Summary: mark messages as read set to 0 leads to occasional read mark skip
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: evolution
Version: 7.0
Hardware: Unspecified
OS: Unspecified
urgent
unspecified
Target Milestone: rc
: ---
Assignee: Matthew Barnes
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 1097268
TreeView+ depends on / blocked
 
Reported: 2014-02-27 14:13 UTC by Vladimir Benes
Modified: 2015-03-05 06:36 UTC (History)
3 users (show)

Fixed In Version: evolution-3.8.5-22
Doc Type: Bug Fix
Doc Text:
Previously, an automatic "mark message as seen" process could fail in certain cases, which caused that a message was not automatically marked after reading. With this update, conditions for the "mark message as seen" process have been corrected, and read messages are now marked as intended.
Clone Of:
Environment:
Last Closed: 2015-03-05 06:36:52 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
evo patch (9.56 KB, patch)
2014-04-08 14:48 UTC, Milan Crha
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 583773 0 None None None Never
Red Hat Product Errata RHBA-2015:0305 0 normal SHIPPED_LIVE evolution bug fix update 2015-03-05 11:36:15 UTC

Description Vladimir Benes 2014-02-27 14:13:10 UTC
Description of problem:
when moving through mails quickly sometimes mails are forgotten to be marked read.

Version-Release number of selected component (if applicable):
evolution-data-server-3.8.5-21.el7.x86_64
evolution-3.8.5-19.el7.x86_64

mark messages as read set to 0 in edit -> preferences -> mail preferences

Comment 2 Milan Crha 2014-02-28 11:05:42 UTC
Upstream patches available within a reference from an upstream bug about the same:

https://bugzilla.gnome.org/show_bug.cgi?id=583773

Comment 3 RHEL Program Management 2014-03-22 05:55:15 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 12 errata-xmlrpc 2015-03-05 06:36:52 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://rhn.redhat.com/errata/RHBA-2015-0305.html


Note You need to log in before you can comment on or make changes to this bug.