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 313712 - new message count on evolution frequently lags
new message count on evolution frequently lags
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
2.32.x (obsolete)
Other Linux
: Normal minor
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks: 543389
 
 
Reported: 2005-08-17 11:37 UTC by Allison Karlitskaya (desrt)
Modified: 2012-01-19 03:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.31/2.32


Attachments
PNG screen capture (12.01 KB, image/png)
2011-09-06 17:17 UTC, Gene Alexander
Details

Description Allison Karlitskaya (desrt) 2005-08-17 11:37:16 UTC
Distribution/Version: Ubuntu Breezy

since a few versions ago (am running 2.3.7) there seems to have been a rework in
the imap code.  mostly this is visible in the fact that on startup evo used to
block for a second or two while it read all of my imap folder statuses and then
displayed them all at once.

in the current version, it displays all of the folders first and you can see
them updating as it queries the server.  this is 'imap', not 'imap4rev1'.

since the time of this change, the new mail count has been incorrect in certain
situations (as if it's not being properly updated).

example:

1) go into evo to see 2 new messages in your inbox
2) erase one of them.  new message count falls to 1.
3) quit evo quickly  (like, press delete then ctrl+w in fairly rapid succession)
4) start evo again and notice that new message count is now 2 again.
5) switch to another folder and back to inbox, still 2.
6) click 'send/receive' and it drops to 1.

it doesn't happen all the time and it's fairly hard to characterise what makes
it happen and what doesn't but some things seem to make it work.  for example,
it doesn't seem to happen if i quit via the window manager close button (have to
use ctrl+w).  it also doesn't seem to happen if you wait around inside evo and
do some stuff after deleting the message before closing.

the other strange thing is, even though the new message count on the folder says 2

  #  Inbox (2)

the new message count at the top correctly says 1:

[ INBOX          117 total, 1 unread ]

anyway... i hope i've provided enough info that you can reproduce it for yourself.

btw: imap server is dovecot 0.99.11.  using it over ssh.

* PREAUTH [CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT
LITERAL+ IDLE CHILDREN LISTEXT LIST-SUBSCRIBED NAMESPACE] Logged in as desrt
Comment 1 Not Zed 2005-08-18 05:07:02 UTC
only after a send/recv will it be correct at that time.

sounds like ctrl-w isn't shutting down properly - i.e. storing things on the
server.  workaround: use ctrl-q instead.
Comment 2 Allison Karlitskaya (desrt) 2005-08-20 21:57:10 UTC
ctrl-q doesn't change anything :(

btw: the things are stored correctly on the server.  it's as if evolution is
keeping some sort of an internal cache that's not correct.
Comment 3 Sebastien Bacher 2005-09-19 07:41:54 UTC
same issue when using the window manager button to close the window
Comment 4 Omer Akram 2010-06-08 07:19:16 UTC
confirming this still happens a few time with 2.30
Comment 5 Omer Akram 2010-06-08 07:19:43 UTC
also reported at: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/21979
Comment 6 Gene Alexander 2011-09-06 17:17:05 UTC
Created attachment 195815 [details]
PNG screen capture

This shows incorrect message count in a Maildir "folder" where all messages have been read and deleted. Folder count shows "5" but the gray title area shows "0 total".
Comment 7 Gene Alexander 2011-09-06 17:18:01 UTC
I am filtering from POP to local Maildir directories with Evolution 2.32.2 and see incorrect message counts in all my "folders" where I just finished reading messages. I will try to attach a screen capture.
Comment 8 Allison Karlitskaya (desrt) 2012-01-19 03:22:23 UTC
I notice that this got fixed a release or two ago and isn't happening for me anymore.  If anyone else is affected, please reopen.