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 571995 - Wrong unread count after filtering
Wrong unread count after filtering
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: Mailer
2.24.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[disk-summary]
Depends on:
Blocks: 543389
 
 
Reported: 2009-02-16 13:46 UTC by Hans Petter Jansson
Modified: 2010-05-22 09:13 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description Hans Petter Jansson 2009-02-16 13:46:59 UTC 
Please describe the problem:
I created a new filter and ran it on my default inbox, causing it to move a bunch of messages from one local mbox to another. There were no unread messages in either mailbox.

When the operation had completed, the source mbox was showing ~150 unread messages in the folder browser, but there are no unread messages to be found in the folder itself.

It *looks* like each message that was moved out of the folder caused its unread count to increase by one. Is the number of mails in the folder being subtracted somewhere, and the difference presented as "unread"?

Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Akhil Laddha 2009-02-17 04:41:19 UTC 
What is exact version of evolution ? Did you try current stable 2.24.4 ? 

You can find 2.24.4 rpms for OpenSUSE 11.1 here

http://download.opensuse.org/repositories/GNOME:/STABLE:/2.24/openSUSE_11.1/
Comment 2 Hans Petter Jansson 2009-02-17 22:49:11 UTC 
Only 2.24.3. Also, the source was in fact not an mbox - it was a vFolder.

I'll try 2.24.4 when I get the chance.
Comment 3 Akhil Laddha 2010-03-26 06:43:09 UTC 
hpj, could you please confirm if this bug is still happening at your end ? Please try in 2.28.x or 2.30.0 and report back, thanks.
Comment 4 Tobias Mueller 2010-05-22 09:13:12 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!