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 591127 - Gmail when configured with Evolutions reports incorrect unread messages
Gmail when configured with Evolutions reports incorrect unread messages
Status: RESOLVED DUPLICATE of bug 559391
Product: evolution
Classification: Applications
Component: Mailer
2.26.x (obsolete)
Other All
: Normal minor
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
evolution[google]
Depends on:
Blocks:
 
 
Reported: 2009-08-08 06:16 UTC by Nicholas
Modified: 2010-11-12 08:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26

Attachments
Screenshot of the evolution bug (81.18 KB, image/png)
2009-08-08 06:17 UTC, Nicholas 		Details

Description Nicholas 2009-08-08 06:16:50 UTC 
Please describe the problem:
I configured my gmail account nichalp@gmail.com in IMAP4 mode with Evolution. Quite often, I notice that the right folder list pane displays unread messages, when infact all my messages are read.

This only goes away if I reboot the system. Closing Evolution and restarting does not solve the problem.

I would like to attach a screenshot of the problem, but the form does not allow me to do so,

Steps to reproduce:
1. Configure a Gmail account using IMAP  
2. 
3. 


Actual results:


Expected results:
Quite often

Does this happen every time?
Quite often

Other information:
Comment 1 Nicholas 2009-08-08 06:17:54 UTC 
Created attachment 140182 [details]
Screenshot of the evolution bug
Comment 2 Akhil Laddha 2010-11-12 08:37:28 UTC 
If possible, please use improved imap support (IMAP+)

Can you please check again whether this issue still happens in Evolution 2.32.0
and update this report by adding a comment and changing the "Version"
field? Thanks a lot.
Comment 3 Akhil Laddha 2010-11-12 08:38:49 UTC 

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