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 687058 - Evolution: I have linked my Gmail a...
Evolution: I have linked my Gmail a...
Status: RESOLVED DUPLICATE of bug 685034
Product: evolution
Classification: Applications
Component: BugBuddyBugs
3.6.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2012-10-28 19:08 UTC by Michael Catanzaro
Modified: 2012-10-28 19:11 UTC
See Also:
GNOME target: ---
GNOME version: 3.5/3.6


Description Michael Catanzaro 2012-10-28 19:08:11 UTC 
I have linked my Gmail accounts to Evolution using GNOME Online Accounts. When I read an email, Evolution may or may not tell Google's IMAP server that I have read the message. Although Evolution marks messages as read while I read them, the next time I open Evolution they are generally marked unread again. After some period of time, Evolution will mark the messages as read on the server.

This occurs in both Evolution 3.4.4 and Evolution 3.6.1 on openSUSE 12.2. Pressing F9 (Send/Receive) once before closing Evolution prevents the bug, but gets annoying. It also happens after a fresh install of the OS, without importing any Evolution data from a backup.

Evolution SEEMS to mark messages as read after maybe six hours or so. (This is wild and unfounded speculation, but that's my timezone offset.) Please don't put too much credibility into this last paragraph!


Distribution: openSUSE 12.2 (x86_64)
Gnome Release: 3.6.1 (null) (SUSE)
BugBuddy Version: 2.32.0
Comment 1 Matthew Barnes 2012-10-28 19:11:24 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 685034 ***