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 634418 - Automatic Mark as Read fails if the first message presented on folder opening is new.
Automatic Mark as Read fails if the first message presented on folder opening...
Status: RESOLVED NOTABUG
Product: evolution
Classification: Applications
Component: Mailer
2.30.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2010-11-09 14:09 UTC by Pedro Villavicencio
Modified: 2010-11-10 03:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.31/2.32



Description Pedro Villavicencio 2010-11-09 14:09:11 UTC
this report has been filed here:

https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/672733

"In Evolution, I currently have it configured to mark a new message as read 0.5 seconds after I open the message. So, for example, I open my inbox folder and there are 50 messages total and 5 marked Unread. I click on one of the 5 Unread messages and open it. Evolution then marks that message as read about 0.5 seconds after I open the message and start reading it.

When I open a folder, evolution opens up a message automatically. IN some cases, this is the last message read, in some cases, it's the first unread message. The bug exists when the second case is met. When I open a folder and evolution automatically opens an Unread message, that unread message is NOT automatically marked read. Instead, I have to open a different message and then return to that message to have it marked Read.

This becomes an even bigger issue when I open a folder that contains exactly ONE message. if I purge the contents of a folder, then get a new message in that folder, I have to use contextual menus to mark the message read, as there is NO way to have it handled by evolution in a automatic method.

For example, please look at the screenshot I have attached.

You'll see my folder for mail from the Laptop Testing Team mailing list at ubuntu.com. I recently purged that folder of all old messages. Then I recieved a new message from that list which was filtered into the folder for Laptop Testing Team.

When I open that folder, the message is opened, however, it is NOT marked as read. Since there is nothing else in that folder, I can't use the workaround of clicking on a different message then clicking back on that message. Thus, the only way to mark the folder as read is to now use context menus on the folder itself."

"Update: Head smack... I forgot that I could mark a message read by clicking on the icon in the messages list.

Be that as it may, the automatic marking is broken in the instances mentioned above, though there are ways to work around it.
"

screenshot:

http://launchpadlibrarian.net/58856296/evolution-auto-mark-as-read-fail.png
Comment 1 André Klapper 2010-11-09 21:51:13 UTC
(In reply to comment #0)
> I have to use contextual menus to mark the message read

Ctrl+K should be faster.
Comment 2 Matthew Barnes 2010-11-10 03:22:26 UTC
Not a bug.  Automatic mark as read is explicitly blocked when a folder is selected.  We do not change the state of the message list without explicit user action within the message list.