GNOME Bugzilla – Bug 583773
Does not always mark mails as read automatically
Last modified: 2014-02-05 17:26:28 UTC
Please describe the problem: I have the "mark mails as read after" option (found under Preferences->Mail Preferences->General) set to 0 seconds. However, if I traverse mails quickly (typically by hitting Ctrl-]), not all mails get marked as read. I can trivially reproduce this; just take a mailbox with many unread mails, rapidly hit Ctrl-], and note that the cursor passes over some mails without marking them as read. Steps to reproduce: Actual results: Expected results: Does this happen every time? Other information:
Originally reported as Debian bug 460827: http://bugs.debian.org/460827
(In reply to comment #0) > Please describe the problem: > I have the "mark mails as read after" option (found under > Preferences->Mail Preferences->General) set to 0 seconds. Note that the setting was removed from the user interface for 3.0. In 3.2 you can edit the value in /apps/evolution/mail/display/mark_seen_timeout via gconf-editor. The value is in milliseconds. From 3.4 on, you can use dconf-editor to edit the value "org.gnome.evolution.mail.mark-seen-timeout".
(In reply to comment #2) > (In reply to comment #0) > > Please describe the problem: > > I have the "mark mails as read after" option (found under > > Preferences->Mail Preferences->General) set to 0 seconds. > > Note that the setting was removed from the user interface for 3.0. Sigh. I just found bug 649597, and added a comment there. In the meantime, this bug still remains: setting the timeout to 0 still doesn't ensure that mails get marked as read immediately when traversing them quickly.
Confirming the issue with both Evolution 3.6.x and 3.9.3, when message preview panel is opened. It seems to be related to how long the preview pane will take to display the email. Sometime, it marks email as read, sometime, it doesn't.. Bumping to 3.9.x
The mark-as-read timer starts from the moment when the message is fully loaded and displayed. If you're traversing mails quickly then you're probably moving on before the message is fully loaded and displayed, which means you couldn't have read the message so the mark-as-read timer for it never started.
Some HTML emails are taking some time to render (don't ask me why, but visibly more than plain text one) and in these cases, I have read the email and still it isn't marked as read. Moreover, when you go through a mailing list thread and you are quickly going from one mail to another, you just want to go next (and have the mail marked as read) even if you don't have read it..
*** Bug 676073 has been marked as a duplicate of this bug. ***
*** Bug 689891 has been marked as a duplicate of this bug. ***
Not sure if it's exactly the same bug. Even when *staying* on the mail it's still not marked as read, I'm not traversing mails.
The problem was that the timer was started when the message was loaded, but not displayed, and the check for "can mark as seen" did require a message to be shown. it means, with timeout 0, that the attempt to mark message as seen was done before the message was shown. The change [1] starts the timer only after the message is loaded and shown in the preview panel, which is the right time for "Mark as seen", because there was a chance to actually see the message. Created commit 51cafd4 in evo master (3.11.5+) [1] Created commit 574a630 in evo gnome-3-10 (3.10.4+) [1] https://git.gnome.org/browse/evolution/commit/?id=51cafd4
One follow-up commit, because I overlooked that the EMailReader is not always an EMailView (the case when opening a message in a separate window, like double-clicking it), which showed a runtime warning on a console: Created commit 1c53fdf in evo master (3.11.5+) Created commit b24bfc8 in evo gnome-3-10 (3.10.4+)
*** Bug 720932 has been marked as a duplicate of this bug. ***